OT: DCOM and RMI

[Jon A. Lambert]

On  1 Jan 98 at 15:32, Chris Gray wrote:
> [Jon L:]
> 
> :I do not rule out ActiveX or DCOM.  However, I have converted my previous
> :client, which was written using VBScript and ActiveX into Java.  The Sun
> :vs. Microsoft lawsuit is very much an extension of the DCOM vs. RMI war. As
> :the agreement between MS and Sun was secret, there is know way of knowing
> :how this will fall out.  You may see DCOM supported by Java in the end as
> :well as RMI.  :P  I can well understand why MS refuses to support certain
> :Java 1.1 extensions.  Oops, I've strayed off signal again...
> 
> Off topic, but, can someone expand on the acronyms 'DCOM' and 'RMI'? I
> know Java, and think I understand what ActiveX is (never seen it tho),
> but I don't know those two.
> 

DCOM stands for "Distributed Component Object Model".  It's largely 
an extension of the ActiveX components.  Which in turn are an extension 
of OLE, "Object Linking and Embedding".  OLE's earliest and most visible 
use to the average user, was the embedding of Excel spreadsheets in
Word documents and in embedding other WinThings in other WinApps.  

It exposes an interface of properties and methods residing and executing
on a server remotely to a client (any C/C++ program) or browser (IE with 
VBScript and/or J++ of course) 

RMI stands for Remote Method Interface which is supported under Sun's
Java 1.1 which allows one to execute a Java method residing on the
server.

DCOM enabled objects are somewhat difficult to write, yet not as 
difficult as CORBA (BTW this is complete hearsay and subjective 
opinion :> ).  

_I_ believe DCOM to be technically superior to RMI in the area
of performance and features.  OTOH, RMI is quite easy to write, 
to call, and understand which is a very big plus.

--
Jon A. Lambert
"Everything that deceives may be said to enchant" - Plato