Hi Michel,

Even if we go for a interface/inheritance based approach is would like to expose tcp_stream/ tcp_connector/tcp_acceptor/udp_stream et al and the like so the user could instantiate a concrete implementation and not going through the address, dynamic factory thingy. There might be specifics in these classes that you care for if you only support tcp eg.

Do you have any specifics in mind? If they are general in nature, they really belong in the interface. Many things can be optionally meaningful even if they are not universal (eg: flush). Best, Don __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com