Dean and Mike, Thanks for the answers. We will be impatiently watching your progress :). Thank you very much and good luck, Andrey On Mon, 10 Dec 2007 22:31:21 -0700, Dean Michael Berris <mikhailberis@gmail.com> wrote:
Hi Andrey,
On Dec 11, 2007 5:00 AM, Andrey Tcherepanov <moyt63c02@sneakemail.com> wrote:
I like the idea of basic_message<> (which could be used for SMTP and gods know what else as well), but what about UDP servers or, generally speaking, multi-transport protocols?
basic_message<> is intended to be divorced from the actual transport being used to put the contents of it out the wire. The idea of basic_message is primarily as a common structure -- or the foundation -- on which all operations lower level (network transport, serialization/deserialization, etc.) and higher level (protocol specific transformations, chaining, stream operations, etc.) will deal with.
[snip]
protocol parsing and transport layer might need more separation. This way if brave person will decide to implement RTSP (for example) as derived from HTTP, he/she will not be limited by TCP transport.
It will be divorced -- the concept of messages have nothing to do with the actual transport and processing that happens in a specific protocol stack.
I hope this helps! :-)