On Mon, 15 Mar 2004 10:30:30 +0000, Tim Bunce wrote:
>
> > ...
> >
> > The problem is reading some types of response messages.
> > When using sockets, the server closes the socket after a
> > sending a response without a Content-Length field. The
> > resulting EOF allows the client to detect that the message
> > is complete.
> >
> > With persistent, unidirectional pipes an EOF is not an
> > option. Now it might be possible to rely on a blank line
> > to indicate the header is complete. However, I see no way
> > to enforce that so I am not going to try.
>
> Doesn't HTTP 1.1 with persistent connections avoid that problem?
Good question. Even with Keep-Alive set, the LWP code will
force the connection to be closed after returning an error.
I did not study it well enough to see how running over HTTPS
changed that.
As I worked on the problem it keep feeling like I was forcing
a square peg into a round hole. So while I wanted the
simplicity of invoke-http-daemon-as-necessary-with-ssh
model, I have to admit that jabber solves problems I'm
tackling very well.
Scott
