Use AMF. http://www.jamesward.org/census/
AMF is much faster. WebORB is cheaper than FDS and has more features. We've used the current version of WebORB it works nice. For 10K/socket WebORB for .NET Enterprise supports AMF3 RemoteObjects, RTMP data pub/sub as well as Media Streaming. Adobe's FDS is 20K/phyical socket and I think FMS(Media Streaming) is like 5K / box? (You'd have to contact Adobe sales for the pricing for the edge edition of FMS which would be the equivalent to WebORB's unlimited Media Streaming connection model.) If you're just looking for RemoteObject support then there''s WebORB Pro for 2K / phsyical. WebORB Enterprise/Professional doesn't support Java/ColdFusion however. This was done on purpose to stay out of Adobe's FDS Java space. If you go with Java you need FDS. Can get a trail version here. http://www.themidnightcoders.com/weborb/ Incidentally the developer mode (which is the default trial mode if you install the trail) allows 5 IP addresses per iisreset which is great for deploying to dev and test. On 1/4/07, jeofmoyster < [EMAIL PROTECTED]> wrote:
I'm looking for any information on why FDS is better than HTTPService or WebService. Or better phrased, WHEN would one prefer FDS over the other two for reasons other than publish/subscription? I'm working on determining the best way to go with an architecture. I can tie Flex applications to Java, .NET or PHP API's for our back-end systems, but I'm wondering whether to go with a home-grown approach/WebORB vs. FDS? Does serving Flex apps from the FDS server reduce bandwidth or make for more efficient delivery? Is polling really terribly detrimental compared to data pushing? Is FDS amazingly faster, better, stronger than going with a free option. How much can an FDS server take before we need to build out the architecture? Basically I need to have a good list of WHY we should use Flex Data Services before I start dropping hundreds of thousands of dollars on the architecture. thanks, /j
