Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I wanted to start a wish list of what we can move forward with, here
is a short list of items that I had in mind as a starter
Here's my opinion on these. I think most of them are not a good idea,
actually.
1. Session replication - stateless backup location
Store the backup location of a session as part of the sessionId,
similar to the jvmRoute but opposite.
This way, you can scale a cluster horizontally, since the location
of the backup node doesn't have to be known until you fail over.
No idea about that.
2. Add a block/no-block parameter to InputFilter.doRead and
OutputFilter.doWrite
InputFilter -> public int doRead(ByteChunk chunk, Request unused,
boolean block) throws IOException;
OutputFilter -> public int doWrite(ByteChunk chunk, Response
unused, boolean block) throws IOException;
Servlet 3.0 will most likely expose non blocking read/write
through the servlet API, this will get us there ahead of time
Haven't thought of how we expose this API yet though, but more
will follow
I think it's too early to speculate on what the Servlet API may add,
and I don't see any benefit this would bring at this point. I am
managing to implement non blocking functionality without major
problems without these additional calls. I also think your API
proposal for Comet in trunk is inappropriate, and I will come back
with my original proposal, which I like more and more. So -1 for this
one.
first you want ice cream, then you don't want ice cream and now you want
ice cream again. one of these days your mommy is gonna tell you to go
straight to bed without dinner. :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
