Re: [Simpleweb-Support] Chat

[berni <be...@t0...>]

Hi Niall,

thank you very much for your help. It does work now.
I just had to remove the commit because that caused a NullPointerException
on the next println.

One more thing:
Is it (technically) possible to get an exception or something if the client
stops loading the page?
Because I need to stop my thread then. Would also make sense for lengthy
database operations - if the client is gone it does not make much sense to
continue working and hogging the CPU. If I am not wrong PHP supports
something like that...

Thank you
Bernhard

----- Original Message ----- 
From: "Niall Gallagher" <nia...@an...>
To: <sim...@li...>
Sent: Wednesday, April 21, 2004 11:25 AM
Subject: Re: [Simpleweb-Support] Chat


> Hi,
>
> This is a bug. I spotted this only a few days ago with the
> MonitoredOutputStream, one workaround that will work is to set the
> connection to close. For instance set your headers like so:
>
> resp.set("Content-Type", "text/html");
> resp.set("Connection", "close");
> resp.commit();
>
> This should enable streaming to work properly. The next release of
> simple (2.4.1) which I will release shortly, will address this bug.
>
> Niall
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Simpleweb-Support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpleweb-support