As promised during my presentation on BlazeDS and ColdFusion 9, here is the code from the presentation. I have also included the slides so you can go through them at your leisure.
In case you missed it. You can see the recording here. BlazeDS and ColdFusion 9...Going Above and Beyond Chat
#1 by Rodion on 4/6/10 - 2:32 PM
I watched your presentation - got lots of new information, thanks.
I got question about messaging, if you allow. As far I understand from preso, messages from BlazeDS are broadcasted to all connected clients simultaneously. If client need only some of broadcasted messages, client should implement some filtering. My question is - since filtering is done on client side, this means that say 'fradulent' client application can receive messages that not intended to be shown on this client. Is it correct ? If yes, can server-side filtering be enabled somehow not to allow certain clients to receive messages not intented to be received.
For example, Twitter client apps are asking for update from server from time to time. If Twitter support messaging, it can 'push' new messages as soon they appear on server. However, if filtering is done on client side, 'fradulent' client app can read some one else's tweets.
Also on Twitter topic - how good BlazeDS is supporting many connected clients - like thousands of simultaneous connections ?
Thanks,
Rodion
#2 by Dave Ferguson on 4/6/10 - 5:02 PM
Couple of things..
Message filtering is done on the server side. That is when consumers register using subTopics or use header filtering. This prevents consumers from getting messages that were not meant for them.
In a couple of my examples I had all messages going to all consumers. The messages where then processed by the consumers and displayed. This was by design in an effort to illustrate a point. I would not suggest this as a best practice or method.
I have not done testing with more than 100 connected clients so I have no idea what the impact of thousands would be.
thanks,
--Dave
#3 by Rodion on 4/6/10 - 5:15 PM
Just one more thing - usually when BlazeDS is described, browser is used as a client. Flex is usually shown as AMF data consumer. What about server-to-server communication using AMF? Can it be performed using Coldfusion on both sides ?
Thanks!
#4 by Dave Ferguson on 4/6/10 - 10:22 PM