Sounds like good advice! I checked out your example implementation so will play around with it tomorrow. Thanks for all of the effort that you put into this library.
> Date: Thu, 5 Sep 2013 19:18:11 +0100 > Subject: Re: Tapestry Server Push/Web Socket/Comet implementation > From: lance.j...@googlemail.com > To: users@tapestry.apache.org > > Note that if you're smart about naming your topics, you can use wildcards. > > eg: if user1 subscribes to /games/game1/user1 and user2 subscribes to > /games/game1/user2 > you can send a message to both users by publishing to /games/game1/* > or you can send a message to all game users via /games/** > > https://github.com/uklance/tapestry-cometd/wiki/Topics > > > On 5 September 2013 18:12, Lance Java <lance.j...@googlemail.com> wrote: > > > If you need to target individual users then you will definitely need a > > topic per user. For game global messages you may decide to use a game > > topic, or you probably know the users in a game and just send a message to > > each user topic. > >
