class Iptuple Store the Local Interface, Local Server Port, Peer Interface and Peer Server Port tuple. More...

Annotated List  Files  Globals  Hierarchy  Index  Top

Public Methods

•  Iptuple ()
•  Iptuple (const char *local_interface, uint16_t local_port, const char *peer_interface, uint16_t peer_port)
•  Iptuple (const Iptuple&)
• Iptuple&  operator= (const Iptuple&)
• void  copy (const Iptuple&)
• bool  operator== (const Iptuple&) const
• const struct sockaddr * get_local_socket (size_t& len) const
• string  get_local_addr () const
• bool  get_local_addr (IPv4& addr) const
• bool  get_local_addr (IPv6& addr) const
• uint16_t  get_local_port () const
• const struct sockaddr * get_bind_socket (size_t& len) const
• const struct sockaddr * get_peer_socket (size_t& len) const
• string  get_peer_addr () const
• bool  get_peer_addr (IPv4& addr) const
• bool  get_peer_addr (IPv6& addr) const
• uint16_t  get_peer_port () const
• string  str () const

Detailed Description

Store the Local Interface, Local Server Port, Peer Interface and Peer Server Port tuple.

Also create the socket buffers to be used by the socket code. All the IP protocol family differences can therefore be hidden in here.

The endpoint addresses can be presented as either numeric addresses or symbolic addresses. Symbolic addresses are converted to numeric addresses and held as such. The symbolic address are kept to aid debugging but are never accessed after the initial conversion to the numeric form. Only in the constructor is there a possibility of a DNS / Yellow pages interaction taking place. After this as we are dealing with IP addresses there should be no danger.

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]

[const]