Hi Adam,
What kind of control of the socket behaviour? lhttpc might be a good
candidate as well as it is steadily building up its feature set with
things which are necessary for couchdb. (like chunked).
Arguably ibrowse is a much mature client supporting a lot of different
options (and lhttpc might not have all the required features yet), but
with the recent introduction of using binaries combined with the long
lived processes inside ibrowse can result in nasty memory blowups as
binaries are reference counted in the VM hence the GC might not be
able to get rid of the huge binaries fast enough during data transfer.
Regards,
Tamas
Tamas Nagy
Erlang Training & Consulting
http://www.erlang-consulting.com
On 4 Jul 2009, at 01:02, Adam Kocoloski wrote:
On Jul 3, 2009, at 7:28 PM, Chris Anderson wrote:
Especially if we can get the replicator based on _changes, and then
truly deprecate the update_notification process
Chandru Mullaparthi gave us a nice assist on that front today with
an update to ibrowse that lets us control the socket behavior. As
far as I know ibrowse is the only Erlang HTTP client that does this
correctly. One month will be more than enough time to build a
replicator based on _changes now that this piece of the puzzle is
resolved.
Adam
