Archived
This forum has been archived. Please start a new discussion on GitHub.
Replicated Object Adapter
vsonnathi
in Help Center
Hi,
In one of the threads almost an year ago:
http://zeroc.com/vbulletin/showthread.php?t=505&highlight=multiple+endpoints
it was mentioned that
"What we would like to do in a future release is add the capability to IcePack to support replication. For example, it might be possible to configure a replicated object adapter, in which case the endpoints for all of the replicated adapters with the same name are combined by the locator."
Is this being considered? The above feature will greatly simplify the deployment and configuration on the Client Side. I don't have to change the configuration whenever I add a new Server.
Thanks,
--Venkat.
In one of the threads almost an year ago:
http://zeroc.com/vbulletin/showthread.php?t=505&highlight=multiple+endpoints
it was mentioned that
"What we would like to do in a future release is add the capability to IcePack to support replication. For example, it might be possible to configure a replicated object adapter, in which case the endpoints for all of the replicated adapters with the same name are combined by the locator."
Is this being considered? The above feature will greatly simplify the deployment and configuration on the Client Side. I don't have to change the configuration whenever I add a new Server.
Thanks,
--Venkat.
0
Comments
-
In the meantime, you could consider using the IcePack object registry and query interface:
- you register your "replicated" (identical) objects with IcePack (this can be done using descriptors, icepackadmin or programmatically -- see IcePack::Admin::addObjectWithType)
- in your client, use IcePack::Query to retrieve one random object with this type (with IcePack::Query::findObjectByType) or all these objects (with IcePack::Query::findAllObjectsWithType) and randomize yourself.
This offers load-balancing but no automatic failover.
Best regards,
Bernard0
