|
Boost : |
From: Iain.Hanson_at_[hidden]
Date: 2001-07-27 07:44:37
Author: scleary (scleary_at_[hidden]) at unix,mime
Date: 26/07/01 20:28
>> The main requirement I see for a C++ socket API is that the protocal
>> (which functions should be invoked in which order) should be
>>enforced
>>I'd like to see if we can find a way to do this without dictating a
>>programming method for the end user.
I agree. I would like to see both saftey and flexability.
[snip ...]
>I'd like to keep as many (asynchronous) options open for the user as
>possible. OTOH, especially if we're aiming cross-platform, maybe we should
>just provide blocking sockets intended for use with Boost.Thread...
The later is the current java model and I find it highly restrictive.
/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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk