Development and Architecture for FMS

Views:
 
Category: Education
     
 

Presentation Description

Best Practices for Development and Architecture for Flash Media Server. Its about Flash Media Server 2.0. General development and live applications best practices. Few Flash Media server resources.

Comments

Presentation Transcript

Slide 1: 

Best Practices for Development and Architecture for Flash and Flash Media Server 2 Presented by: Graeme Bull Macromedia MAX 2005 — Hong Kong 11/17/2005

What’s new in Flash Media Server 2? : 

What’s new in Flash Media Server 2? New name (was Flash Communication Server) Better performance Partial message handling etc Improved Tunneling Better/Easier Manageability Improved Logging Native support for SSL Use other server side scripting php/asp web services

What’s new in Flash Media Server 2? : 

What’s new in Flash Media Server 2? Multiple process support for applications and instances Increases stability and efficiency Edge Servers increases scalability options New and improved admin panel File Object Improved security functionality Support for XML socket streams

What are we talking about here? : 

What are we talking about here? Best Practices and architecture   for Flash and FMS2 can be   broken into two main areas Server settings and config Application Level (coding/planning)

Server settings and configuration : 

Server settings and configuration What we can do to make the server run more efficiently and faster What we can do to make the applications run efficiently and safer for the server

Application Level (coding/planning) : 

Application Level (coding/planning) What type of planning we need to do before starting a new application Always depends on the type of application that will be built What coding practices we should be thinking about

General Development Best Practices : 

General Development Best Practices Take advantage of Server Side code as much as possible Use AS2 and organize the classes used for the application with the SS code Keep code/classes independent of each other for portability Create components or “copy and paste code” for quicker and easier development

Best Practices for Live Applications : 

Best Practices for Live Applications Plan for all scenarios, disconnects, network problems, mic/cam problems Keep the application aware of it’s state at all times Also, make sure the user is aware of the state the application is in at any point (buffering, connecting etc)

A few examples : 

A few examples Creating a unique ID for clients Initiate the client onConnect Keep an array of client objects Take advantage of the XML object or loadVars Use virtual keys for streaming video Breakup functionality with different script files

FCS Resources : 

FCS Resources Macromedia resources http://www.macromedia.com/devnet/mx/flashcom/ http://livedocs.macromedia.com/fms/2/docs/ Flashcomguru http://www.flashcomguru.com Peldi's blog site: http://www.peldi.com/blog/ My blog site: http://www.sti-media.com/blog/