Hi Tom -
There is some overlap in functionality between FMS and FDS - as both
products evolve, we will all get a better sense of which use cases each
is better suited to.
However, I can definitively say that FMS is NOT being put out to
pasture in any way.
In fact, we have nearly doubled the
why not stick with fms.Our apps get enourmous amounts of usage (MySpace is one of our clients) and we were hoping FDS would scale better. Using Java instead of single-threaded _javascript_ for our server-side logic should improve things significantly. If we can support the same features and it
Ah, a slightly different use-case for sure.
I haven't tried it, but I would think I could do this in a filter.
When the user should get banned, place a message onto say your JMS
bus. The filter is subscribed to ban messages where the userid = the
current userid. Now inside the filter I simply
hmmm...The fact that all anyone can really think of are theories suggests to me that FDS may not really be an optimal platform where centralized intelligence is required. It sounds like FMS really still has a strong position for these kinds of apps. Of course FDS does have some nice benefits as
clueless insight
Placing a J2EE security constraint on the assets in FDS and then
setting a timout on the J2EE session isnt sufficient?
/clueless insight
--
Dave Wolf
Cynergy Systems, Inc.
Adobe Flex Alliance Partner
http://www.cynergysystems.com
http://www.cynergysystems.com/blogs
Email:
The most common reason we need to disconnect a client is because the user has been banned from the chat by an administrator for behaving inappropriately. We're an ASP that hosts chat and im apps and we let our clients configure timeouts on a per-user basis. We have to have a way to manage
6 matches
Mail list logo
