Chapter 5: Developing Social Media Applications; Shared Objects - Adobe 65029121 - Flash Media Streaming Server Developer's Manual

Chapter 5: Developing social media
applications
In addition to streaming video applications, Adobe Flash Media Interactive Server and Adobe Flash Media Devel-
opment Server can host social media and other real-time communication applications. Users can capture live audio
and video, upload them to the server, and share them with others. These server editions also provide access to remote
shared objects that synchronize data between many users, and so is ideal for developing online games.
You can use Server-Side ActionScript to connect to other systems, including Java 2 Enterprise servers, web services,
and Microsoft .NET servers. This connectivity allows applications to take advantage of services such as database
authentication, real-time updates from web services, and e-mail.
In addition to these advanced techniques, social media applications can take advantage of the video development
techniques described in Developing media
Note: The majority of this chapter is only applicable to Flash Media Interactive Server and Flash Media Development
Server, as Adobe Flash Media Streaming Server does not support server-side programming.

Shared objects

About shared objects
Use shared objects to synchronize users and store data. Shared objects can do anything from holding the position of
pieces on a game board to broadcasting chat text messages. Shared objects let you keep track of what users are doing
in real time.
With Flash Media Interactive Server or Flash Media Development Server, you can create and use remote shared
objects, which share data between multiple client applications. When one user makes a change that updates the
shared object on the server, the shared object sends the change to all other users. The remote shared object acts as a
hub to synchronize many users. In the section
move.
Note: Flash Media Streaming Server does not support remote shared objects.
All editions of the server support local shared objects, which are similar to browser cookies. Local shared objects are
stored on the client computer and don't require a server.
Shared objects, whether local or remote, can also be temporary or persistent:
•
A temporary shared object is created by a server-side script or by a client connecting to the shared object. When
the last client disconnects and the server-side script is no longer using the shared object, it is deleted.
• Persistent shared objects retain data after all clients disconnect and even after the application instance stops
running. Persistent shared objects are available on the server for the next time the application instance starts. They
maintain state between application sessions. Persistent objects are stored in files on the server or client. See "Setting
the location of recorded streams and shared objects" on page 32.
applications.
SharedBall example, when any user moves the ball, all users see it
ADOBE FLASH MEDIA SERVER
Developer Guide
51