tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remy Maucherat <r...@apache.org>
Subject Re: Comet changes
Date Wed, 09 May 2007 16:22:50 GMT
Filip Hanik - Dev Lists wrote:
> true. lets see how it pans out in actual code, that might change our 
> perspective.
> 
> I was toying around with an alternative idea too, disallow any read or 
> write all together unless it is done on a worker thread. gives us 
> complete control, easier to implement.
> 
> public void CometEvent.notify(int operations);
> 
> operations = READ | WRITE | NOW;
> 
> READ - this is what we do now under the covers, this would give the user 
> the control, basically means, notify me when there is data to read
> WRITE - notify me when I can write data
> NOW - send me a worker thread my way, so that I can safely initiate a 
> blocking or non blocking read or write.

Ok, so it would call notify(WRITE) when the write "available" flag 
becomes false. Also, do you have any idea of another name for the 
"notify" method ?

Rémy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message