Cirrus 2 and Flash Player 10.1 / Air 2
Codename Cirrus enables peer assisted networking using the Real Time Media Flow Protocol (RTMFP) within the Adobe Flash® Platform. RTMFP is the evolution of media delivery and real time communication over the Internet enabling peers on the network to assist in delivery.
The most important features of RTMFP include low latency, end-to-end peering capability, security and scalability. These properties make RTMFP especially well suited for developing real-time collaboration applications by not only providing superior user experience but also reducing cost for operators.
In order to use RTMFP, Flash Player endpoints must connect to an RTMFP-capable server, such as the Cirrus service. Cirrus is a beta, hosted rendezvous service that aids establishing communications between Flash Player endpoints.
Unlike Adobe Flash Media Server, Cirrus does not support media relay, shared objects, scripting, etc. So by using Cirrus, you can only develop applications where Flash Player endpoints are directly communicating with each other.
What's new in Currus 2
Support for RTMFP Groups — Allows clients to easily participate with other clients in a network in order to share the transport of media and communications without maintaining a connection to every peer in the group. Groups can be defined by their functionality and access can be controlled by the client application.
Overlay network — Allows clients to easily find each other without using network probing.
Support for live Application-Level Multicast — Allows a publisher to deliver a live media stream and scale the stream delivery as wide as needed. Application-level multicast reduces the load on a single publisher, and distributes the delivery over multiple peers. This functionality is designed for a small group of peers broadcasting large messages (i.e. higher bitrate data).
Support for Directed Routing — Allows a developer to create communication applications and send data messages to a specific peer in the group.
Support for Posting — Allows a developer to broadcast data messages to all peers within the group, but lacks reliability and ordered delivery. This is useful for data broadcasts applications such as instant messaging, game play or even sensor reporting such as weather station updates. This functionality is designed for lots of peers broadcasting small messages (i.e. low bitrate).
Support for Object Replication — Allows a developer to create a applications such as workspace replications, whiteboards or sharing data between peers. Object replication allows for the reliable and orderly delivery of data over the RTMFP group.
The most important features of RTMFP include low latency, end-to-end peering capability, security and scalability. These properties make RTMFP especially well suited for developing real-time collaboration applications by not only providing superior user experience but also reducing cost for operators.
In order to use RTMFP, Flash Player endpoints must connect to an RTMFP-capable server, such as the Cirrus service. Cirrus is a beta, hosted rendezvous service that aids establishing communications between Flash Player endpoints.
Unlike Adobe Flash Media Server, Cirrus does not support media relay, shared objects, scripting, etc. So by using Cirrus, you can only develop applications where Flash Player endpoints are directly communicating with each other.
What's new in Currus 2
Support for RTMFP Groups — Allows clients to easily participate with other clients in a network in order to share the transport of media and communications without maintaining a connection to every peer in the group. Groups can be defined by their functionality and access can be controlled by the client application.
Overlay network — Allows clients to easily find each other without using network probing.
Support for live Application-Level Multicast — Allows a publisher to deliver a live media stream and scale the stream delivery as wide as needed. Application-level multicast reduces the load on a single publisher, and distributes the delivery over multiple peers. This functionality is designed for a small group of peers broadcasting large messages (i.e. higher bitrate data).
Support for Directed Routing — Allows a developer to create communication applications and send data messages to a specific peer in the group.
Support for Posting — Allows a developer to broadcast data messages to all peers within the group, but lacks reliability and ordered delivery. This is useful for data broadcasts applications such as instant messaging, game play or even sensor reporting such as weather station updates. This functionality is designed for lots of peers broadcasting small messages (i.e. low bitrate).
Support for Object Replication — Allows a developer to create a applications such as workspace replications, whiteboards or sharing data between peers. Object replication allows for the reliable and orderly delivery of data over the RTMFP group.
Comments
Post a Comment