From: Hugo Duncan (hugoduncan_at_[hidden])
Date: 2002-11-25 10:43:26
On 24 Nov 2002 20:49:06 +0000, Hamish Mackenzie <hamish_at_[hidden]> wrote:
A write on an ssl stream can
> block attempting to read from the underlying socket (and vice-versa).
Not sure I fully understand this. Could you elaborate please.
is want_read equivalent to "Would Block On Write" ?
> Another tricky issue with openssl is the ability to have different read
> and write file descriptors for an ssl connection.
Is this effectively using one socket for communication in each direction?
ie non-duplex operation ?
> In my opinion socket_exception should derive from std::exception.
> However what() should return nothing more than "socket error". The
> reason for this is that any more information like "dns lookup error for
> host xyz.abc.com" could reveal sensitive information about ones network.
Not sure that his is the right place to be hiding information
> I like the idea of having an error policy
So do I. What is the reasoning for passing socket_function and args ?
I have aded a preliminary ErrorPolicy, without the arguments to handle_error.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk