[
https://issues.apache.org/jira/browse/WICKET-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504093#comment-13504093
]
Emond Papegaaij commented on WICKET-4879:
-----------------------------------------
I don't see how you could return true for one client and false for another
(other than using something like random). filter() is used with no receiver
context at all. It is meant to be used to filter certain types of events (other
than the actual instance type). For example, if you have an event that contains
progress of a job and you only want your component to receive the events if the
progress is 80% or higher, that's when you use filter(). The same filter should
always return true for the same events.
Can you take a look at commit a5421ec488020a3835d49962e1f772dc1435e230? I've
added methods to post an event to a single resource, either with a resource
instance or via its uuid (which I think makes more sense). You can get the UUID
with AtmosphereResource.getUUID(page).
> Implementing channels in wicket-atmosphere
> ------------------------------------------
>
> Key: WICKET-4879
> URL: https://issues.apache.org/jira/browse/WICKET-4879
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-atmosphere
> Affects Versions: 6.3.0
> Environment: Tomcat / Jetty
> Reporter: Zala Goupil
> Assignee: Emond Papegaaij
> Fix For: 6.4.0
>
> Attachments: wicket-atmosphere-quickstart.zip
>
>
> Good evening,
> Now that both Tomcat & Jetty support native WebSockets, it would be a
> killer-feature to implement Comet / WebSockets channels. i.e. being able to
> have a channel id and to post a message to one client only or to all the
> clients who subscribed to a certain channel.
> For the moment, it is possible to do it, but to the (expensive) price of
> having a PerRequestBroadcastFilter and tweaking it if we manage to do it. But
> it would be great to have a link to the Broadcaster API from Atmosphere,
> which I think, supports this kind of things.That would probably be way more
> efficient than PerRequestBroadcastFilter tweaking.
> As of today, when posting a message to the event bus, all pages who have the
> @Subscribed-decorated method suitable to process this message will do it,
> which is not always desirable.
> I'm looking forward to hear from you.
> Regards
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
