From: Dean M. B. <mik...@gm...> - 2009-11-29 18:33:37
|
Hi Guys, I'm doing some consulting work right now which allowed me to implement an HTTP Server template which thankfully I've gotten a go-signal to opensource under the Boost Software License. This is not the same HTTP server template that I developed in Friendster -- I'm still waiting for them to release that as open source -- and this implementation heavily borrows from the Boost.Asio server 3 example (although is header only). Glyn, how are we doing with releasing version 0.4? I'll request a merge from my urllib-dean branch into integration_0_4 so that we can finally merge back to trunk and release version 0.4 that uses Boost.Spirit 2.1. TIA and HTH -- Dean Michael Berris blog.cplusplus-soup.com | twitter.com/mikhailberis linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com |
From: Glyn M. <gly...@gm...> - 2009-11-29 20:27:58
|
Hi Dean, 2009/11/29 Dean Michael Berris <mik...@gm...> > Hi Guys, > > I'm doing some consulting work right now which allowed me to implement > an HTTP Server template which thankfully I've gotten a go-signal to > opensource under the Boost Software License. > Cool. This is not the same HTTP server template that I developed in > Friendster -- I'm still waiting for them to release that as open > source -- and this implementation heavily borrows from the Boost.Asio > server 3 example (although is header only). > Are these two different implementations of the same thing or do you intend to do some merge on the differences? I'm looking forward to seeing this. > > Glyn, how are we doing with releasing version 0.4? I'll request a > merge from my urllib-dean branch into integration_0_4 so that we can > finally merge back to trunk and release version 0.4 that uses > Boost.Spirit 2.1. > Please feel free to do the merge. John sent me a off list saying that he didn't want to contribute any longer and, since his branch has diverged a long way, I don't expect we'll be able to reintegrate it. For 0.4 I wanted: A URI package with unit tests The HTTP client using the new URI (which you say you just completed) Better docs Better examples I would therefore say we're pretty close, short of the documentation. I'm afraid I can only commit a small amount of time in the next couple of weeks, but I will try and make progress with the documentation so as not to hold up the release. (Also, please feel free to pass comment on the current docs in integration_0_4). I take a holiday on the 17th Dec so I expect to release before then. G |
From: Dean M. B. <mik...@gm...> - 2009-11-29 22:00:27
|
Hi Glyn, On Mon, Nov 30, 2009 at 4:27 AM, Glyn Matthews <gly...@gm...> wrote: > Hi Dean, > > 2009/11/29 Dean Michael Berris <mik...@gm...> >> >> Hi Guys, >> >> I'm doing some consulting work right now which allowed me to implement >> an HTTP Server template which thankfully I've gotten a go-signal to >> opensource under the Boost Software License. > > Cool. > Indeed. :) >> This is not the same HTTP server template that I developed in >> Friendster -- I'm still waiting for them to release that as open >> source -- and this implementation heavily borrows from the Boost.Asio >> server 3 example (although is header only). > > Are these two different implementations of the same thing or do you intend > to do some merge on the differences? I'm looking forward to seeing this. > They're almost the same, although the version I'm releasing in a few hours is a little more simplistic in its implementation than the Friendster version. I'm going to be following up on that version with some of my friends in Friendster, hopefuly they can get to it sooner than later. In the meantime I'd love to get help evolving the implementation to a point where it's ready for "full featured production use". >> >> Glyn, how are we doing with releasing version 0.4? I'll request a >> merge from my urllib-dean branch into integration_0_4 so that we can >> finally merge back to trunk and release version 0.4 that uses >> Boost.Spirit 2.1. > > Please feel free to do the merge. John sent me a off list saying that he > didn't want to contribute any longer and, since his branch has diverged a > long way, I don't expect we'll be able to reintegrate it. > That's a shame. I really hope he would consider contributing at a later date following the conventions and techniques being used in the implementation now. > For 0.4 I wanted: > > A URI package with unit tests I think we have this now although the tests are not enough yet. > The HTTP client using the new URI (which you say you just completed) Yup. :) > Better docs I can try helping out in this regard since I like writing a lot anyway. ;) > Better examples I'll see if I can come up with more of these. > > I would therefore say we're pretty close, short of the documentation. I'm > afraid I can only commit a small amount of time in the next couple of weeks, > but I will try and make progress with the documentation so as not to hold up > the release. (Also, please feel free to pass comment on the current docs in > integration_0_4). > No pressure, and thanks for letting us know of your availability. Maybe someone else can help out in the documentation effort? > I take a holiday on the 17th Dec so I expect to release before then. Alright, I'm gunning for a Dec. 10 paper to be submitted for BoostCon and a presentation on the various techniques used in the library. In particular I'm looking at the following: * Tag-based header-only delineation and implementation (one of the more misunderstood techniques of the library) * Directive-based DSEL for message building * Fluent interface for protocol interfaces I intend to share progress on the paper to both the Boost Developers mailing list and our mailing list as I go along in writing the paper. I'm thinking of using Google Docs for that effort too. Thanks and I hope this helps! -- Dean Michael Berris blog.cplusplus-soup.com | twitter.com/mikhailberis linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com |