[omniORB] Versioning of objects

[Stefan Seefeld]

klarson@McLeodUSA.com wrote:
> 
> I have been unable to find much information on how to version objects.  For my
> application, I will have multiple clients accessing the same CORBA objects.  If
> I need to modify an object (let's say one of the clients needs a new method or
> some new data) it would be very difficult (impossible?) to coordinate the
> release of my new object with a release of all of the client applications.  I
> would think there should be some way to version an object so that all clients
> can use the new object as long as the modifications are such that it is backward
> compatible.  I would think that this would be a common requirement for users of
> CORBA, but have been unable to find much information about how to accomplish
> this.  Is there any mechanism in OmniOrb to facilitate this?  Does anyone have
> any suggestions on how to accomplish this?  Any help would be greatly
> appreciated!

I think the number at the end of the Repo ID was originally inteded to be used
for versioning. For some obscure reason the OMG abstained from that though.

What you might use is a trader where you offer objects and attach versions as
properties to them. Then clients can choose whatever version they support.

Regards,	Stefan
_______________________________________________________              
              
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: seefelds@magellan.umontreal.ca

_______________________________________________________

      ...ich hab' noch einen Koffer in Berlin...