Newsgroups: comp.object,comp.lang.java,comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!swrinde!howland.reston.ans.net!ix.netcom.com!netcom.com!schwamb
From: schwamb@netcom.com (Karl Schwamb)
Subject: Re: Interaction of Corba and Java
Message-ID: <schwambDn8FJz.BAA@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <4fo55p$qkh@reuter.cse.ogi.edu> <3124B66C.4A6C@ccm.jf.intel.com> <AD4FB3629668187D5F@mac-sandvik.engr.sgi.com> <312B549A.7DCC@ccm.jf.intel.com>
Date: Fri, 23 Feb 1996 14:14:23 GMT
Lines: 19
Sender: schwamb@netcom8.netcom.com
Xref: glinda.oz.cs.cmu.edu comp.object:44958 comp.lang.java:26396 comp.lang.smalltalk:35141

Patrick Logan <patrick_d_logan@ccm.jf.intel.com> writes:

>At least two people have misinterpreted my use of the term "migrate".

>The definition I am using above is "migrate an object at run-time from one
>process to another."

>The definition people may be confusing this with is "migrate a legacy system
>from an implementation in one language to an implementation in another".

>I agree that CORBA/COM both address the latter definition. I am interested in
>the former more than the latter.

CORBA already addresses object migration under the object lifecycle
service.  Objects can be moved or even copied.  I believe Sun's NEO
already implements this service and other ORB vendors are working on it.
See "The Essential Distributed Objects Survival Guide" by Orfali, Harkey, and
Edwards for more info.

