From: Dean M. B. <mik...@gm...> - 2008-09-03 06:39:46
|
On Wed, Sep 3, 2008 at 2:24 PM, Allister Levi Sanchez <all...@gm...> wrote: > > On Wed, Sep 3, 2008 at 7:12 AM, Dean Michael C. Berris > <dmb...@fr...> wrote: >> >> This time I think we may have to move the mime processing code outside >> of boost/network/protocol and just move it into boost/network/utils or >> something similar. A lot of the URI parsing stuff can also be moved out >> of boost/network/protocol/http and into its own component into >> boost/network/utils. > > Hmmm, isn't MIME itself a protocol > (http://en.wikipedia.org/wiki/Category:Application_layer_protocols)? > Oh, right. :D My bad. :) > And speaking of utils, the message encoding/decoding (such as to/from base64 > that you have in http) could also be added there, right? > Yes, Base64 encoding (not yet implemented) will have to go into utils. >> >> I'll think more about it before making any changes/moves. >> >> It would also be a good idea to branch off for MIME development >> (mime_integration) perhaps. >> >> More about it as my brain starts picking up. ;) > > Yes, maybe branching off for MIME would be a good idea -- once we've decided > where to put it hehe... > I think you're correct with putting mime into protocol/ -- I imagine it would need to be split up to multiple files and in its own directory protocol/mime/ aside from just protocol/mime.hpp ? -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |