I think you could use a Bayeux solution here, where messages are sent/ delivered to clients that have subscribed to channel(s). I think both atmosphere and cometd support this, in the later case that is all they support.
On Jan 17, 1:54 pm, Captain Haddock <[email protected]> wrote: > Newbie Q .. what is the correct approach to the following application: > > - multiple client applications show an icon representing the state > (good or bad) of 1 or more resources (lets say client 1 shows resource > A, client 2 shows resources A and B, client 3 shows resources B and C) > - the state of those resources is determined on the server side > through some independent thread (not related to any client request) > - when the status of the resource changes, I want to push that change > to the clients showing that resource > > At first glance, I thought Atmosphere should provide mechanisms to do > what I want .. but all the examples seem to have everything triggered > from the client (browser) side. In my case other than the client > registering interest in particular resources (A and/or B and/or C), > the client does not initiate anything. > > Am I forced to make the client (long) poll? I was rather hoping for > some level of abstraction where I can set initial interest by > registering some listener against some subject and after that just > publish updates from the server without my server code having to have > an explicit handle to a client (I was assuming some toolkit would > handle that). > > If appropriate, pointers to any examples would be great. All the chat > examples I can find seem to initiate stuff from the client. > > Not much help from the Atmosphere code which lacks javadoc. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
