RE: [boost] Note about a socket/network library

From: Iain.Hanson_at_[hidden]
Date: 2001-08-03 04:40:20

Author:  jonkalb (jonkalb_at_[hidden]) at unix,mime
Date:    02/08/01 19:36

[snip]
     
>My guess would be that worrying about XTI/TLI APIs would be a needless 
>complication for a socket library, but if Iain has some insight into a 
>design that can be implemented to support both API's without adding too 
>much complexity or compromising performance or portability, I say "power 
>to 'im."

If the differences were significant, I would be the first one to duck 
:-).

XTI/TLI has predominantly a one to one call equivilence with sockets 
i.e.:

t_open = socket
t_bind = bind
t_listen = listen
t_accept = accept
t_connect = connect

and so on.

There may be some parameter coercion necessary, but that should not be 
too much of a problem. This all comes from memory ( I wrote a TLI streams 
driver a little while ago ), so, once I do the analysis, if I see any 
problems, I'll come back to the group on it.

/ikh
     
     
     
     

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.