Ah, that may well be the case. I thought that the browser kept it open until the site was left or the window closed but I can certainly see how it might make sense to close it when done rendering. Oh well.

Hrm. If the browser does indeed close the connection after rendering the page, what about opening your own connection manually via javascript? Are javascript sockets automatically closed when the page is closed / unloaded? I would think they would be, so that means you could perhaps simply open a connection to a "keep alive" server, stick it in a globally scoped variable, and then just forget about it. I haven't done enough with javascript sockets to know if this is feasible. Alternatively, you could perhaps use a hidden frame that never finishes rendering to accomplish the same effect.

bbfu
Black flowers blossom
Fearless on my breath


In reply to Re^3: GUI with HTTP::Daemon by bbfu
in thread GUI with HTTP::Daemon by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":