Slide by slide description of how LCDS works. Created during a training session. Came out well so uploading it as it is

1. LCDS 3.1- how it works
Yash Mody
CTO | Tekno Point
yash@teknopoint.us

2. SWF Client
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>

3. SWF Client
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>
Message
(IMessage)

4. Message
SWF Client (IMessage)
Channel
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>

5. SWF Client Message
(IMessage) Channel
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>
END Point

6. MessgaeBrokerServlet
OR
NIO/RTMP Socket
SWF Client Message
(IMessage) Channel END Point
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>

7. MessageBroker
MessgaeBrokerServlet
OR
NIO/RTMP Socket
SWF Client Message
(IMessage) Channel END Point
<mx:RemoteObject/>
<mx:DataService/>
<mx:Producer/><mx:Consumer/>
Security constraints
are handled here.
Responsible for
Authentication

8. Invoke Service
MessgaeBrokerServlet
MessageBroker
OR
•RemotingService
NIO/RTMP Socket •HTTPProxyService
•MessagingService
.. Client
Message
Channel
(IMessage) END Point •DataService
Security constraints
are handled here.
Responsible for
Authentication

9. MessgaeBrokerServlet Invoke Service
MessageBroker
OR
Destination is
NIO/RTMP Socket like an instance
of a service
Message
Channel END Point Destination
.. Client (IMessage)
Security constraints
are handled here.
Responsible for
Authentication

10. MessgaeBrokerServlet Invoke Service
MessageBroker
OR
Destination is
NIO/RTMP Socket like an instance
of a service
Message
Channel END Point Destination
.. Client (IMessage)
Adapter/
Assemblers
Security constraints Serves request locally (invokes
are handled here. a class) or connects to a back-
Responsible for end(Hibernate/Assembler) or
Authentication connects to a remote server
(JMS)

11. Thank You