[ 
https://issues.apache.org/jira/browse/WICKET-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503397#comment-13503397
 ] 

vineet semwal commented on WICKET-4879:
---------------------------------------

see code below,i mean something like this,you can change/improve according to 
your usecase

 public class InputWrapper<T> {
        /**
         *
         * @param input
         * @param id  id is sessionid of sender
         */
        public InputWrapper(T input, String  id){
            this.input=input;
            this.sender=id;
        }

        public T getInput() {
            return input;
        }

        public String getSender() {
            return sender;
        }

        T input;
        String sender;
    }

    /**
     * compare sessionid and return true if session id of sender is same as 
receiver
     */
    public static class SomePredicate implements Predicate<InputWrapper>{
        @Override
        public boolean apply(@Nullable InputWrapper wrapper) {
            return wrapper.getSender().equals(Session.get().getId());
        }
    }


                
> 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

Reply via email to