From: Dean M. B. <mik...@gm...> - 2008-11-02 19:36:42
|
Hi Rodrigo, Sorry it took a while for me to respond. Please see in-lined below. (BTW, next time please avoid overquoting and top-posting.) On Sun, Nov 2, 2008 at 6:06 AM, Rodrigo Madera <rod...@gm...> wrote: > Thanks again. > However the current architecture is not generic enough. It feels like HTTP > was the only protocol thought about during it's design. That's odd, the message abstraction is very generic -- it doesn't assume anything about the protocols that will be using it. The structure of a message is really very flexible, and using tags you can even completely revamp the way a basic_message<> will look like (and how the interface would be) for your context/protocol. It would be nice to know why you think the architecture is not generic enough when being as generic as possible is what the whole library was designed to be. > I'll post my progress here. Please do, this will be very interesting to us. Thanks and have a good day! -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |