Hi Peter,

sorry, for late writing. Thank you for your long mail. Normally I want to write code with vim to get a better understanding how it work. The same I want to do with the gnu development tools. So I suppose it needs a little bit longer as I was supposing. The other side is to get familize with the code.

About your design issue:

On Monday it came in my mind that maybe only one buffer is needed. Maybe we need two SocketBuffer but the class has only one buffer with read and write and not one SocketBuffer with two buffers - one for read and one for write.

Which makes me wonder whether it would make sense or not to split the Transport interface in two separate interfaces – Connection and Buffer?

This is really great! You have find out two task which do not really combinded together. To hold a class small and understandable I agree with you. Seperate it!

@atul: I know the State pattern and can remember on the original example. But I think and have read that for this scenario which is described the GoF in their book the TCPConnection was overwhelmed. Do we need really states here?

To my person: I am working as a C++ developer for two years. At the moment I have only time at the weekend.

Regards,

Markus