Terminology and Portability Terminology and Portability (Web host 4 life) This book
Terminology and Portability Terminology and Portability This book does not try to cover every aspect of IPv6 technology the book constrains itself to the IPv6-capable programming on top of socket API. There are numerous reading materials on IPv6 technology, so readers are encouraged to read them before starting to work on this book. Also, the book assumes a certain level of expertise in socket API programming. The book does not try to explain every aspect of socket API programming; please read the material listed in the References for an introductory description to socket API. Terminology and Portability This section describes notations and terminologies used in this book. Here we also discuss porting issues of examples when you are using operating systems that are not 4.4BSD variants. Terminology System calls and system library functions are usually denoted by UNIX manpage chapters: socket(2) or printf(3). Nodes means any IP devices. Routers are any nodes that forward packets for others. Hosts are nodes that are not routers (however, in this book, we don t really need to make distinctions between them). Portability of Examples The examples in the book compile and run on latest *BSD releases. I tried to make the examples as correct as possible. If you are planning to use the examples on other platforms, here are some tweaks dependent on OS implementations. Solaris, Linux, Windows XP struct sockaddr has no sa_len member. Therefore, it is not possible to get the size of a given sockaddr when the caller of the function passed a pointer to a sockaddr. The only ways to work around this problem are: 1. To always pass around the length of sockaddr separately on function calls:
We feature a web hosting shopping cart and live support solution. Just try our web hosting shopping cartwhich provides a secure way of obtaining payments through your website.