Hi,
Ryan J wrote:
> Hi,
>
> I'm starting to consider how I'm going to design a portion of my application. I
> guess the best way to describe it would be:
>
> A queue shared between multiple application clients / users.
>
> I can think of two ways to do this...
>
> 1. Use the messaging system to publish changes relevant to the queue to
> subscribed application clients.
>
> 2. Have each application client poll the server (refresh) at regular intervals.
>
> I'd like to know if anyone has any thoughts / comments relating to either
> strategy. I have a preference, but would like to see what other people think
> before I start.
Is your client web application (or does is support the http protocol)?
If yes, you might want to consider Comet programming. See [1] and [2] if
you are interested.
Thanks
-- Jeanfrancois
[1]
http://weblogs.java.net/blog/jfarcand/archive/2007/05/new_adventures.html
[2]
http://weblogs.java.net/blog/jfarcand/archive/2006/07/the_grizzly_com.html
>
> Ryan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>