Lots of discussion this weekend on the costs associated with the bandwidth required with some uses of the Flash Communication Server.
- Flash Comm Server and Bandwidth Costs…
- John Dowdell’s comments
- Would you like bandwidth with that Flash Communication Server?
- Round 2: Flash Communication Server v. The Socket Servers
- Flashcom and the Dedicated Bandwidth Option
- Total Cost of Flash Comm Server
- Flashcomm Bandwidth Explained
Unfortunately, broad conclusions are being drawn on Bandwidth requirements based on very specific scenarios (i.e. streaming video 24 hours a day).
Some uses of the Flash Communication Server can be very bandwidth intensive. In particular, streaming audio and video takes a lot of bandwidth. This should not come as a surprise to anyone, and is not something unique to the Flash Communication Server. So, if you have to get your access from a hosting provider, and are using the Flash Communication Server for non-revenue generating projectors, then you need to be very careful about the amount of audio and video you stream. Btw, Aral points out that for Flash Communication Server projects that require a lot of bandwidth, dedicated bandwidth can be a much, much cheaper option than hosting.
However, while streaming audio and video is the feature of the server that everyone is talking about, it is not necessarily the main feature. In fact, from a developer’s standpoint, I think the ability to easily (almost effortlessly) connect multiple Flash clients is the coolest feature of the Flash Communication Server. The problem is that this is something that the end product (connected flash movies) is something that can be done with XML today (and thus is not as sexy). However, it is much, much easier using the Flash Communication Server (no need to parse XML, send and receive ActionScript data types, etc…), as well as much more efficient. In fact, for large multiuser projects, you will probably save on bandwidth costs using the Flash Communication Server verses using XML (mostly because XML is so verbose).
So, I think that the point that all of the articles are trying to raise, is that before embarking on a project, you need to consider all of your costs; development, resources, server and bandwidth. If you plan to stream large amounts of audio and video, then you need to pay particular attention to your bandwidth costs / estimates.
Thoughts? Comments? Post them in the comments section.