Bill Sanders Answers Flash Communication Server Questions

Getting Started with Flash Communication Server

Flash Communication Server lets developers build applications that send and receive audio, video, and data in real time. Bill Sanders has spent years helping people set up the server, write ActionScript, and keep the flow smooth. If you are new to the platform, the first step is to install the server and make sure the environment is ready for coding. The installer brings along a web‑based administration console that shows the current server state, available ports, and logged‑in users. Once the console is up, you can test a simple connection by opening a browser and navigating to the default URL. The server will present a welcome page that confirms it is listening on the configured port, usually 1935 for RTMP traffic.

The next phase is to decide whether you want to host the server on a dedicated machine or on a shared hosting platform. If you choose the former, you will have full control over the server configuration files. The key file, server.xml, contains a list of applications that the server can host. Each application entry includes a path, a policy file location, and a flag that indicates whether the application is enabled. Bill recommends keeping the applications separate from the core server binaries to simplify upgrades. Once the server is running, the next challenge is to create a simple client that can communicate with it. This is where shared objects come into play.

Shared objects act like a real‑time database that synchronizes state across all clients that connect to the same application. For example, if you drag an image in the client, the server pushes that change to everyone connected to that URL. The code for a shared object is straightforward. You first instantiate it by calling SharedObject.getLocal with a unique name. Then you bind to the onSync event to react when other clients make changes. Bill’s sample code shows a small demo that uses a shared object to keep a counter in sync across multiple users. The demo runs in Flash Player 10 or later and demonstrates how to set the shared object to persistent or non‑persistent mode depending on your needs.

Once you feel comfortable with shared objects, it is time to explore media streaming. Flash Communication Server supports both audio and video streaming over RTMP. The server can serve MP3 files directly, meaning users never have to download the file before playing it. Instead, the server streams the audio in chunks that the player buffers on the fly. To enable MP3 streaming, you must place the MP3 file in a directory that the server can read, and then call the server’s streaming API from ActionScript. Bill’s tutorials walk through the API calls for startStreaming, stopStreaming, and setStreamingQuality. The quality parameter controls the bitrate, so you can adjust the stream speed to match your users’ bandwidth. For video, the same principles apply, but you also have to consider codecs and container formats. Flash Player supports H.264 in MP4 containers, so you can encode a video with a low bitrate and high compression, then stream it to clients that can decode it without hiccups.

The last piece of the puzzle is to set up security. Flash Communication Server supports policy files that govern cross‑domain access. A policy file is an XML file that lists which domains are allowed to connect to the server. Bill recommends creating a separate policy file for each application, rather than a global one, to keep the security tight. Once the policy file is in place, the server will read it on each new connection. By examining the source code, you learn how to structure applications, where to place shared objects, and how to manage media streams programmatically. For developers who prefer visual learning, the book’s companion website hosts video tutorials that walk through key concepts. These videos cover topics like installing the server, creating policy files, and scripting the server side logic. The pacing is slow enough for beginners, yet fast enough to keep advanced developers engaged. The official Flash Communication Server documentation remains the authoritative source for configuration details. It contains exhaustive descriptions of every XML tag in the server.xml file, a full reference for the RTMP stream parameters, and guidelines for writing server‑side ActionScript. Bill has provided annotated excerpts from the official docs in his blog posts, translating the technical jargon into everyday language. These annotations help you understand the purpose of each setting without getting lost in the documentation’s formal style. Moreover, the documentation’s API reference is searchable, which speeds up development when you need to find a specific method or property. The documentation’s FAQ section is an invaluable tool, reducing the need to sift through documentation for every small query. Once you are comfortable with the trial, you can purchase a full license that removes the connection cap and unlocks advanced features like live recording and integration with external databases.

Flash Communication Server Book

The published book “Flash Communication Server” by Bill is a comprehensive guide that covers every aspect of the platform. The book starts with a gentle introduction to the server’s architecture, explaining how the RTMP protocol works and how the server interacts with Flash Player. Each chapter focuses on a different type of application - live audio, live video, real‑time data, and collaboration. The author includes step‑by‑step instructions, sample code, and screenshots that make it easy to follow along. The book also dedicates a section to performance tuning, covering topics like server capacity planning, load balancing, and monitoring. Bill’s practical advice on setting bandwidth limits, managing connection quotas, and scaling shared objects ensures that you can deploy applications in production environments without unexpected bottlenecks.

The publisher provides downloadable sample projects that match the examples in the book. These projects are fully functional and can be run on your local machine. They include both client Flash files and server ActionScript scripts, so you can see how the two parts work together. By examining the source code, you learn how to structure applications, where to place shared objects, and how to manage media streams programmatically. For developers who prefer visual learning, the book’s companion website hosts video tutorials that walk through key concepts. These videos cover topics like installing the server, creating policy files, and scripting the server side logic. The pacing is slow enough for beginners, yet fast enough to keep advanced developers engaged.

Beyond the book, Bill maintains an online repository of sample applications and code snippets. The repository is hosted on a version‑control platform, so you can fork it, make changes, and push your own iterations. Bill encourages you to contribute back any improvements or fixes, creating a collaborative environment that benefits everyone. The repository also includes a FAQ section that answers questions such as “How do I enable cross‑domain policy?” or “What is the best practice for persistent shared objects?” For quick answers, the FAQ is an invaluable tool, reducing the need to sift through documentation for every small query.

The official Flash Communication Server documentation remains the authoritative source for configuration details. It contains exhaustive descriptions of every XML tag in the server.xml file, a full reference for the RTMP stream parameters, and guidelines for writing server‑side ActionScript. Bill has provided annotated excerpts from the official docs in his blog posts, translating the technical jargon into everyday language. These annotations help you understand the purpose of each setting without getting lost in the documentation’s formal style. Moreover, the documentation’s API reference is searchable, which speeds up development when you need to find a specific method or property. The data collected during these tests informs the adjustments you need to make before moving to a production server. Once you are comfortable with the trial, you can purchase a full license that removes the connection cap and unlocks advanced features like live recording and integration with external databases.

Security is crucial when you move an application to production. Bill stresses the importance of configuring TLS for RTMPS traffic if you are handling sensitive data. While Flash Communication Server traditionally uses RTMP over TCP, the RTMPS protocol adds an SSL layer that encrypts the entire stream. To enable RTMPS, you must install a valid SSL certificate on the server and then update the server.xml file to listen on port 443. The configuration also requires a valid policy file that specifies the HTTPS domain. By using RTMPS, you can protect both your media streams and your data messages from eavesdroppers. Bill’s guide to setting up TLS includes detailed steps for creating a certificate, updating the server configuration, and testing the secure connection from a client. Finally, joining the Flash Communication Server community can accelerate your learning. There are online forums, user groups, and conference sessions where developers share tips and tricks. Bill frequently presents at conferences and has a strong presence on the community’s mailing list. By subscribing to the mailing list, you receive regular updates on new releases, security patches, and best‑practice articles. The community also hosts open‑source projects that demonstrate creative uses of shared objects, such as collaborative drawing boards and live scoreboards. Reviewing these projects gives you ideas for your own applications and shows how others solved common problems. By leveraging these community resources, you can quickly find answers to any question you have and see how other developers have implemented complex use cases.