We are also investigating adding dynamic destination support on top of the selector technique.
Matt -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Bray Sent: Wednesday, March 29, 2006 11:28 AM To: [email protected] Subject: Re: [flexcoders] Message destinations in the context of a multi-room chat app I was able to answer my own question. In my original post I didn't realize that the selector attribute of the Consumer component filtered messages on the server side. So, Stefan, if you want see what I'm talking about, check out the sample chat application supplied with the FDS installation. In the chat.mxml file, change this line: <mx:Consumer id="consumer" destination="chat-topic-jms" message="messageHandler(event)"/> by adding a selector attribute: <mx:Consumer id="consumer" destination="chat-topic-jms" message="messageHandler(event)" selector="room='Lobby'"/> and then in the send() function, add a message header called room with a value of "Lobby" like so: public function send():void { var message:AsyncMessage = new AsyncMessage(); message.headers.userId = userId; message.headers.msg = msg.text; message.headers.room = "Lobby"; producer.send(message); msg.text=""; } So, you'll have just one destination called chat-topic-jms, but that destination can serve multiple rooms by using a selector. The server only sends messages to clients that are both subscribed to that destination and have specified a matching selector. Let me know if that makes sense. Thanks, Tom On 3/28/06, Stefan Richter <[EMAIL PROTECTED]> wrote: > > I haven't actually had a chance to play with FDS yet (and I am unfamiliar > what exactly a destination is in this context) but what you describe sounds > like a definite limitation. Would you be able to post some code that shows > how and where this problem surfaces? > > Stefan > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Tom Bray > Sent: 29 March 2006 00:49 > To: [email protected] > Subject: Re: [flexcoders] Message destinations in the context of a > multi-room chat app > > > Stefan, it's nice to know I'm not alone over here! > > Regarding using FMS and FDS together, I'd like to be able to rebuild this > app: > > http://www.userplane.com/webchat/ > > using FDS for all the text messaging and data synchronization and FMS > for the live AV. So far, I don't see a clear path to that goal > without dynamic destinations or some equivalent approach. Remote > Shared Objects in FMS are essentially dynamic destinations the way we > use them in our apps. > > -Tom > > > > On 3/28/06, Stefan Richter <[EMAIL PROTECTED]> wrote: > > > > Good question and one for Adobe to answer - and I don't mean the specific > > implementation but: where does FMS/FCS stop and FDS start? Should we > really > > be building chat apps with FDS? I'm sure I am not the only one still a > > little confused by the crossover of functionalities. > > > > Stefan > > > > > > BTW hello list, long time lurker first time poster here > > > > > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > > Behalf Of Tom Bray > > Sent: 28 March 2006 20:19 > > To: [email protected] > > Subject: [flexcoders] Message destinations in the context of a multi-room > > chat app > > > > > > I've been trying to understand how to configure destinations in the > > context of a multi-room chat application where the rooms are > > dynamically created. Here's the scenario: > > > > The application loads a configuration file that specifies what rooms > > to create. In this case, let's say that list includes the rooms > > Lobby, Sales, and Support. In additon to these dynamically created > > rooms, individual users can create new rooms from within the > > application. > > > > My first thought was that each room would be a message destination > > (topic), but it doesn't appear that destinations can be dynamically > > created. Then I thought I'd have a single destination but use > > selectors on the consumer component to determine which room's messages > > should be displayed in the chat output area, but that would mean that > > all messages for all rooms would go to all clients whether they were > > in that room or not. > > > > How would you handle this? > > > > I'm coming at this from the perspective of a Flash Communication > > Server developer and I'm trying to figure out if what I've done in FCS > > can be replicated or, hopefully, surpassed with FDS. > > > > Thanks, > > > > Tom > > > > > > -- > > Flexcoders Mailing List > > FAQ: > > > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > > > > > > ________________________________ > > YAHOO! GROUPS LINKS > > > > > > Visit your group "flexcoders" on the web. > > > > To unsubscribe from this group, send an email to: > > [EMAIL PROTECTED] > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. > > > > ________________________________ > > > > > > -- > Flexcoders Mailing List > FAQ: > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > > ________________________________ > YAHOO! GROUPS LINKS > > > Visit your group "flexcoders" on the web. > > To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. > > ________________________________ > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
