Lines Matching full:network

28 .\".ds RH "Network Library Routines
36 3. NETWORK LIBRARY ROUTINES
42 locate and construct network addresses when using the
47 to manipulate network addresses.  While the 4.4BSD networking
61 into network \fIaddresses\fP which are not necessarily suitable
65 network architectures.  For instance, it is desirable for a network
68 the client host.  Instead, underlying services in the network
77 to network addresses, network names to network numbers, 
98 #define	h_addr	h_addr_list[0] 	/* first address, network byte order */
173  * The network number below is the one for the NS net
192 Network names
194 As for host names, routines for mapping network names to numbers,
200  * Assumption here is that a network number
207 	int	n_net;	/* network number, host byte order */
211 and \fIgetnetent\fP(3N) are the network counterparts to the
215 NS network numbers are determined either by asking your local
216 Xerox Network Administrator (and hardcoding the information
219 that needs to manipulate network numbers on a regular basis; if
250 the Internet domain, but inconsistent with other network architectures.
261 	int	s_port;	/* port number, network byte order */
296 services to be developed as much as possible in a network independent
297 fashion.  It is clear, however, that purging all network dependencies
298 is very difficult.  So long as the user is required to supply network
300 network dependency in a program.  For example, the normal
307 a layer of routines which masked the network dependent aspects from
316 swapping of network addresses and values.
328 htonl(val)	convert 32-bit quantity from host to network byte order
329 htons(val)	convert 16-bit quantity from host to network byte order
330 ntohl(val)	convert 32-bit quantity from network to host byte order
331 ntohs(val)	convert 16-bit quantity from network to host byte order
339 system expects addresses to be supplied in network order (aka ``big-endian'' order).  On
342 network byte ordering.  Consequently,
344 library routines which return network addresses provide them
345 in network order so that they may simply be copied into the structures
347 byte swapping problem only when \fIinterpreting\fP network addresses.