- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi Greg,
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.
hope that helps
nigel
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.
hope that helps
nigel
Views
Replies
0 Likes
Total Likes