I apologize if this ground has already been covered. I'm obviously late to the dicussion.
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Chris Cleeland
[snip]
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. -Greg