Hello Michael,
On 09/02/2011 05:07 AM, Michael Raab wrote:
> ok. But beside the problem of passing the information (the shutdown command)
> from client to server, what is the best (or a stable) way for closing the
> connection between those two in a clean way on both sides. Of course without
> interfering all other connected servers.
hmm, I'm assuming you can coordinate the shutdown command with the sync,
so the server does not shut down in the middle of a sync. Then it should
mostly be a matter of removing the server from ClusterWindow's
GroupConnections (see below). Depending on what information your custom
window keeps about the connected servers you may have to recalculate
that of course, since now there is one server less.
> Unfortunately I'm not that familiar with the OpenSG1.8 network communication
> classes. :-(
neither am I...
but there is GroupConnection::disconnect(Channel c) to remove a remote
point from a GroupConnection, which should do what you are looking for.
Cheers,
Carsten
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
