The only changes that you need to worry about are changes to the published behavior. I don't see a reason not to replace ibrowse if it fixes that bug for you.
Paul On Thu, Sep 23, 2010 at 6:36 AM, Filipe David Manana <[email protected]> wrote: > Oh, btw, for got to mention, the only 2 cases we have in CouchDB for > streaming chunked HTTP responses are when listening for _changes of a > remote DB and getting attachments from a remote DB. > > On Thu, Sep 23, 2010 at 11:34 AM, Filipe David Manana > <[email protected]> wrote: >> Hi all, >> >> Recently, I upgraded ibrowse in trunk (from 1.5.1 to 1.6.2). >> >> The reasons were several (check the README of ibrowse - >> http://github.com/cmullaparthi/ibrowse). >> I did it on 1.0.x as well since it adds an important bug fix for the >> proxy support feature. >> >> However, I recently found that it had a serious issue when streaming >> chunked responses (with {stream_to, {pid(), once} option) - >> http://github.com/cmullaparthi/ibrowse/issues/closed#issue/7 >> >> Chandru, ibrowse's author, just committed a fix for this and added at >> the same time more changes, upgrading ibrowse from version 1.6.2 to >> 2.0.0 - >> http://github.com/cmullaparthi/ibrowse/commit/d756a2b0b6a792639c5f4fad7db1fe461e6d3634 >> >> I definitely want to upgrade trunk to use ibrowse 2.0.0. >> However I'm unsure if we should do it for 1.0.x as well, since adds >> more changes then the streaming of chunked responses fix. >> >> Let me know your opinions. >> >> cheers >> >> >> -- >> Filipe David Manana, >> [email protected], [email protected] >> >> "Reasonable men adapt themselves to the world. >> Unreasonable men adapt the world to themselves. >> That's why all progress depends on unreasonable men." >> > > > > -- > Filipe David Manana, > [email protected], [email protected] > > "Reasonable men adapt themselves to the world. > Unreasonable men adapt the world to themselves. > That's why all progress depends on unreasonable men." >
