On Sun, Oct 03, 2010 at 08:12:21PM -0500, Nolan Darilek wrote: > I've been sporatically experiencing the hung sync operations I've > written about here before. Maddeningly, sometimes the problems disappear > on their own without any changes on either side, and at others, they > went away with --httptrace. I finally seem to have a hung sync that > fails even with --httptrace, though.
I think part of the problem is the fossil server reports HTTP/1.0 and also gives a connection:close header and also doesn't close the connection but instead waits for the client to do it. Really, it should be HTTP/1.1, Connection:close, always have a Content-Length:, and then the server closes the connection when it's sent the Content-Length: of data. Then I think a lot of the hangs I see wouldn't happen. -- Zed A. Shaw http://zedshaw.com/ _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
