Boost logo

Boost :

From: Mr Minh (m_phanivong_at_[hidden])
Date: 2005-08-20 11:49:43

These are the two most important improvements.

> * The use of the word "Stream" can be confusing because its existing
> association in C++ with iostreams. Can anyone suggest an
> alternative?

The use of "stream" in this context seems natural enough for me. I
suspect most people writing networking code will agree.

> * Should stream_socket and dgram_socket be merged into a single socket
> class? There other types of sockets (e.g. sequenced packet) that
> would require additional classes if the current approach is
> retained. This would not be required if the BSD socket APIs were
> covered by a single class. Alternatively, should additional classes
> be added for the other socket types?

My instinct tells me that they shouldn't be merged: they are very
different concepts, and I wouldn't like this specific abstraction
eliminated in asio.

would it be more logical to have a basic_socket_stream class and then have socket_type_traits for tcp_socket_trait, udp_socket_trait and seq_socket_trait..

a tcp_socket_stream can be a a basic_socket_stream with the trait of tcp_socket_trait.. aka basic_string -> string

just an idea.


Minh Phanivong
+64 2 136 7118 (NZ)

"Instead of living in the shadows of yesterday, walk in the light of today and the hope of tomorrow. "

Send instant messages to your online friends

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