Jerome, You make a lot of sense.
I agree with you that Jetty's solution is complicated, but I was 1) hoping we could do it more straightforwardly in Restlet (possibly a naive hope), and 2) a graph (and other) solutions would have their own complexity. There's really no simple way out of this. That said, the graph approach is programatically more comprehensible, and also more idiomatic to Java, than simulating continuations. (I'd also add that functional languages would make this problem much more comprehensible, but I'm afraid that Tim would bite my head off, so I won't...) I was also thinking of the problem in a far more local sense -- a single thread "committing" -- rather than the more complex scenarios you've listed, of chunked responses, which I imagine would be extremely useful in the new streaming applications to which Restlet is being applied, with Noelios' terrific new partnerships. So, yes, I'm fully in agreement with the graph approach, it is comprehensive and can potentially address all needs. So, it'll be ready next week? ;) Happy new year! ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2903175
