[
https://issues.apache.org/jira/browse/WICKET-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503977#comment-13503977
]
Zala Goupil commented on WICKET-4879:
-------------------------------------
Good evening,
I've just tried it. The behaviour is the same: if three clients are connected
and that only one's filter returns true, then the same message goes to all the
three clients. If two of them return true, then those two send the message to
the three clients, and so on.
Personally, I'd like to be able to have the message sent by one client
broadcasted to only this client. Of course, the use case of "one client sends
to all" is useful, I just wish it was not the only one possible.
Anyway, your "contextAwareFilter" is useful, thanks for that !
I've tried myself to implement a Broadcaster-based message-sending in your
code, but for the moment, I failed. Too bad. The one thing I miss is how to
provide an AtmosphereResource to my Broadcaster.
Anyway, keep up the good work! :-)
> 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
