Something else to consider is that there might be better tools for
doing what you need to do. It sounds like WebSockets might be a better
match for you. Unfortunately, I'm not at all familiar with using this
in the Java world, so I can't provide any Java-specific pointers.

But lately I've been dabbling with Node.JS [1] and Socket.IO [2].
Might be worth looking into. The great thing about Socket.IO is that
it supports Javascript clients all the way back to IE5.5, and could
save you a bunch of client-side work.

On Fri, Apr 29, 2011 at 12:16 PM, Gili <cowwoc_at_bbs.darktech.org> wrote:
> Jakub,
>
> Thank you for that link! Atmosphere is exactly what I had in mind. This
> brings up the question: does this "Reverse-Ajax" model suffer from the
> economies of scale problem mentioned by Roy Fielding in [1]?
>
> [1] http://roy.gbiv.com/untangled/2008/economies-of-scale>
> Thanks,
> Gili
>
>
> Jakub Podlesak-2 wrote:
>>
>> Another problem here is even the StreamingOutput does not save you from
>> running out of the Java threads.
>> If you want a scalable solution, you would need to somehow re-use the
>> threads to be able to serve
>> all the long open connections. Some work in this area was done by Paul
>> Sandoz and Jean-Francois Arcand
>> with project Jersey and project Atmosphere. An example is available at
>> [1].
>>
>> ~Jakub
>>
>> [1]http://atmosphere.java.net/nonav/xref/org/atmosphere/samples/twitter/TwitterResource.html#80>>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/Entity-streams-tp6314573p6317967.html> Sent from the Jersey mailing list archive at Nabble.com.
>