Might the Cocomo architecture include functionality that
makes Cocomo apps more robust to the underlying NetConnection being
closed than Flash/FMS apps?
I ask because we have an existing Flash/FMS chat and video
application that we consider an ideal candidate for conversion to
An issue that we have encountered with the current
implementation is occurrences, on active connections, of:
info.code == "NetConnection.Connect.Closed"
As I indicated, these events are not occurring due to idle
connections. Also, our preliminary analysis shows that the network
is still live (e.g. users are able to immediately log back in).
I realize that Cocomo does not expose functionality at this
level. However, if Cocomo may include functionality making Cocomo
apps more robust to the underlying NetConnection being closed, then
this will help greatly in getting the green light for the
conversion from management.
Nigel Pegg, Nov 25, 2008 9:40 AM
Cocomo does implement retry logic and client migration to a
different FMS server in case of failure and we are continuously
improving the level of robustness of the system, so that should
keep your application clean and more resilient to failures.
As you and Raff note, we don't want you to have to care
about NetConnection management - it's one of the things Cocomo
handles for you. Raff has it right - if a Cocomo client
unexpectedly gets a NetConnection.Connect.Closed, it simply
reconnects to the server and gets back to work. If you need to
expose some UI to indicate something like this is happening,
IConnectSession exposes synchronizationChange events as well as the
isSynchronized property (true if connected and synched to the
service, false if it's been cut off). Most collaboration components
(Chat, etc,) also expose these events/properties.