ref the socket around the processing of the message, since otherwise it
authorDan Winship <danw@src.gnome.org>
Sun, 28 Oct 2007 17:23:38 +0000 (17:23 +0000)
committerDan Winship <danw@src.gnome.org>
Sun, 28 Oct 2007 17:23:38 +0000 (17:23 +0000)
commit2fcfaa9f21de3ddb4fab6c4e444f1437b249b55c
tree85cf9e2f33cab0af317a31332da8fe1a808f0698
parentcb3563f19e8be5d0e898f5badc4bea4c5c9d7cd1
ref the socket around the processing of the message, since otherwise it

* libsoup/soup-server.c (start_request, request_finished): ref the
socket around the processing of the message, since otherwise it
might already be freed when request_finished runs. #459896.

* libsoup/soup-message-io.c (soup_message_io_pause)
(soup_message_io_unpause): Clarify the docs here; this is for
server-side use only. Inspired by #452280.

* docs/reference/server-howto.xml: You need to watch the
"finished" signal on the message if using soup_message_io_pause()
or chunked encoding, because the client might disconnect while
you're paused. Clarification inspired by #471385.

* tests/simple-proxy.c (client_msg_failed): Fix this to DTRT since
server-howto.xml points to it as an example of what to do.

svn path=/trunk/; revision=947
ChangeLog
docs/reference/server-howto.xml
libsoup/soup-message-io.c
libsoup/soup-server.c
tests/simple-proxy.c