[omniORB] object versioning
Renzo Tomaselli
renzo.tomaselli@eclipse-net.it
Wed, 13 Jan 1999 12:07:42 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_00CD_01BE3EED.5284AAB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi there,
as a developer of a distributed imaging application which makes use =
of OmniORB I run into some maintenance issues since the application is =
packaged into a number of dlls connected through a dynamic loader. =
Everything works fine as far as OmniORB is concerned. It happens that =
modules which have indipendent life but some form of dependency (A calls =
B methods) run into incompatibility problems such as changing a method =
signature because IDL design changed but runtime or installation made a =
poor job. A quick screening of OmniORB sources pointed out as the =
version field of Interface Rep. Id is not used and it seems also that =
IIOP doesn't transmit IntfRepID along requests. Woudn't it be a good =
choice for version control of interdipendent objects ? Would it violate =
any CORBA specs to have it transmitted from client stubs to the server =
so that the implementation skeleton can check it against its own, =
refusing to dispatch unmatched versions ?
Comments are welcome,
Renzo =
Tomaselli =20
-------------------------------------------------------------------------=
--
TecnoTP s.n.c. Special Information System Design
Maso Pelauchi I38050 Ronchi Valsugana, Trento TN ITALY
Tel. +39 0461 773164 Fax. +39 0461 771514
e-mail: renzo.tomaselli@eclipse-net.it =20
-------------------------------------------------------------------------=
--
------=_NextPart_000_00CD_01BE3EED.5284AAB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3007.2"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi there,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> as a developer of =
a=20
distributed imaging application which makes use of OmniORB I run into =
some=20
maintenance issues since the application is packaged into a number of =
dlls=20
connected through a dynamic loader. Everything works fine as far as =
OmniORB is=20
concerned. It happens that modules which have indipendent life but some =
form of=20
dependency (A calls B methods) run into incompatibility problems such as =
changing a method signature because IDL design changed but runtime or=20
installation made a poor job. A quick screening of OmniORB sources =
pointed out=20
as the version field of Interface Rep. Id is not used and it seems also =
that=20
IIOP doesn't transmit IntfRepID along requests. Woudn't it be a good =
choice for=20
version control of interdipendent objects ? Would it violate any CORBA =
specs to=20
have it transmitted from client stubs to the server so that the =
implementation=20
skeleton can check it against its own, refusing to dispatch =
unmatched =20
versions ?</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>Comments are=20
welcome,</FONT></DIV>
<DIV><FONT color=3D#000000=20
size=3D2> &nbs=
p;  =
; =
&=
nbsp; &n=
bsp; =20
Renzo Tomaselli =20
<BR>---------------------------------------------------------------------=
------<BR>TecnoTP=20
s.n.c. Special Information System Design<BR>Maso Pelauchi I38050 Ronchi=20
Valsugana, Trento TN ITALY<BR>Tel. +39 0461=20
773164 Fax. +39 0461 771514<BR>e-mail: <A=20
href=3D"mailto:renzo.tomaselli@eclipse-net.it">renzo.tomaselli@eclipse-ne=
t.it</A> =20
<BR>---------------------------------------------------------------------=
------</FONT></DIV></BODY></HTML>
------=_NextPart_000_00CD_01BE3EED.5284AAB0--