[cpp-netlib-devel] Some thoughts, XMPP work etc.

[Reetesh M. <ree...@gm...>]

Hi Dean and All,

I have been going through the code development in cpp-netlib for last 6
months. I have been experimenting on XMPP for a while, (
http://tarang.xmpp.googlepages.com/) and have done some crude
implementations (see svn). With time, I am planning to stick to cpp-netlib
codes, for their is no meaning of implementing things in XMPP which are
already in cpp-netlib. That said, now onwards I will like to put my view
points (and also codes in cpp-netlib ;-) ), for it will have direct impact
on XMPP design. I have some points in my mind:-


   1. basic_message<...> class resembles basic_string<...> class. I think
   this class very well fits in the whole scheme. However I could not
   comprehend the intent of _source, _destination. In particular cases they can
   be mail-id, server-id; some kind of classes. They need not be necessarily
   std::string.
   2. basic_message<...> should be serializable over asio sockets.
   3. There can be derived classes from basic_message<...> ---
   basic_receiver_message<...>, basic_sender_message<...>. For
   basic_receiver_message we can have functions like:-
   read(socket&,basic_receiver_message<...>&) or read_until(socket&,
   basic_receiver_message<...>&). Here read_until does not contain any
   delimiter because basic_receive_message<...> will have this information.
   Similar will be the functions around basic_sender_messag<...>
   4. In future there should be modules to parse basic_message<...> using
   boost::regex or boost::spirit or boost::xpressive.


Moreover we need project branches for rtp, rtsp, also. Though yes our prime
requirement is http.

Regards,
Reetesh Mukul