Boost logo

Boost :

From: Hickman, Greg (greg.hickman_at_[hidden])
Date: 2006-01-11 11:45:22

I apologize if this ground has already been covered. I'm obviously late
to the dicussion.

> -----Original Message-----
> From: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]] On Behalf Of Chris Cleeland


> really using. I don't see how one can get hold of the raw
> socket descriptor to twiddle options that the library
> hasn't abstracted.

Would a viable approach in this case be to provide platform-specific or
"hidden" socket options as "optional" public interface according to
whether those options are available on a given platform?

On a related note, should a general-purpose socket library really couple
socket classes to an event demultiplexer? Although Asio is more than a
socket library, my first inclination would have been to build the socket
abstractions independently of auxiliary concepts in such a way as to
allow users to combine their usage in the manner most appropriate for
their applications. And it does seem like that approach would lead to a
socket handle accessor on the public interface of socket classes.


Boost list run by bdawes at, gregod at, cpdaniel at, john at