Duncan Grisby dgrisby at uk.research.att.com
Mon Feb 7 06:45:20 EST 2000

• Previous message (by thread): Communicating with MICO
• Next message (by thread): GCOM, was Re: Communicating with MICO
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

In article <slrn89n1ev.vdn.kc5tja at garnet.armored.net>,
 Samuel A. Falvo II <kc5tja at garnet.armored.net> wrote:

>In article <87bl08$nui$1 at pineapple.uk.research.att.com>, Duncan Grisby wrote:
>
>>I prefer omniORBpy, but I wrote it so I'm not exactly unbiased.
>
>I may be talking to you in the future about this, if you don't mind.  As
>you're probably aware, I'm working on a COM implementation for Linux called
>GCOM.  The IDL for it will be based on CORBA's own IDL, and I plan on using
>GIOP for communications between local servers.  Remote servers are handled
>via GIOP-IIOP bridges (called ORBs ... go figure!).

I'm happy to talk about omniORBpy and all things CORBA. From your
description of GCOM, it sounds just like a CORBA ORB. In what way is
it a COM implementation?  Do you intend to interoperate with COM /
DCOM, or just follow some of the design?

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --

---

• Previous message (by thread): Communicating with MICO
• Next message (by thread): GCOM, was Re: Communicating with MICO
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list