I presume you are refering to WICKET-4879, There are no examples of the new API yet, but the changes are not that big. I did not really implement channels, but made the changes that would allow you to implement channels. It is now possible to post an event to a single client (rather than all clients), either via the AtmosphereResource for that client, or its UUID. I also added a contextAwareFilter() to @Subscribe, which allows you to access the RequestCycle and session from the filter. This can be used to differentiate on the receiver of the event, where filter() can only be used to differentiate on the content of the event. Be careful with this new method though, because it will not scale very will with large numbers of concurrent users.
Looking at the code again, I think I'm going to change the Predicate into a Function on AtmosphereResource. That would allow you to keep track of some attributes in AtmosphereRequest on which to write your filter, which puts a lot less weight on the server than setting up a RequestCycle. Best regards, Emond Papegaaij On Thu, Dec 20, 2012 at 8:31 PM, Noven <noven_...@yahoo.com> wrote: > Hi, > > I just saw new features released at wicket 6.40. And I am interested to > see example code of the atmosphere channel. Where can i find the example of > this feature? > > Thanks. > >
