[
https://issues.apache.org/jira/browse/WICKET-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503505#comment-13503505
]
Zala Goupil commented on WICKET-4879:
-------------------------------------
Unfortunately, my experience is that if a predicate matches for a client and
doesn't matches for the others, the matching predicate sends the response to
all clients. So in our case the message is sent only once, and not as many
times as there are connected clients, but to all the connected clients. Which I
find pretty annoying.
Regarding my exception, it only happens when using complex HTML, in one of my
projects, it is totally absent. But in another one, it happens on a regular
basis.
> 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
> 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
