Skip to content

#360Flex Notes – “Building real time applications with Blaze DS/LCDS” – Dan Blackman

The why?!?
CF request/response applications
Flex RIA
persisted data is not refreshed automatically
stateful approach to managing data – no more sessions
refreshed through manual client interactions or AS
Flex Real-time Apps
persisted data is refreshed via interactions w/ server
stateful approach w/ server side sync
refreshed through polling, long polling, or RTMP
data management service – life cycle service – provides data sync between clients

Intro to LCDS
consists of: flex messaging service, flex data management, flex proxy service, and remote object service

Push vs Pull
pull is client asks server for data
push is server actually pushing data to client

Types
Simple AMF
– stateful approach
RTMP – real time messaging protocol
maintains persistent connection
allows real time
uses java-nio facilities
Polling
flex client sends requests for messages periodically

Configuring channel/destination
-CFGateway: messages sent between cf8/flex
-JMS Adapter: allows to use both JMS/Flex clients to communicate
-AS Adapter: flex default allows only flex clients to participate in communication

Channels
my-cf-amf
cf-polling-amf
cf-long-polling-amf
cf-streaming-amf
cf-rtmp

Examples using LCDS (chat) and then CFGateway (Facebook notifications)

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*