Date: Tue, 9 May 2000 22:55:21 +0500 (GMT-5)
From: Sergey Izvoztchikov <[EMAIL PROTECTED]>
On Wed, 10 May 2000, Mark Kettenis wrote:
> Indeed. I don't really have experience with CORBA, but I don't think
> the issues in this thread are relevant in this stage of Hurd
> development. Right now the core Hurd protocols are defined by the MiG
> .defs files. At one side this defines the C ABI, at the other side
> this defines the layout of messages and conventions on how to handle
> the data contained in them for use with Mach IPC. None of these can
> be easily changes without rewriting most of the Hurd.
First thought was that Hurd should have its ORB to be treated
an Enterprise level OS. I heard about possibility of inter-computer
communications using Mach messages, but I suspect it doesn't function
in Hurd now.
I started with studying Flick from FLUX which theoretically allows
to generate Mach3 IPC from CORBA IDLs. And I think that using
CORBA allows mush more people start writing new servers and porting
existing software to Hurd. It's just more convenient way for programmers
who already knows CORBA.
Well, if all you're interested in is porting an existing CORBA
implementation (like ORBit) to the Hurd, you'd be more than welcome.
However, take a look at the Debian/Hurd project first. It might
already have been done :-).
If you think it is possible to make things more efficient by doing the
actual data transfer directly via Mach IPC, that might indeed be
something worth exploring.
However, *replacing* MiG with CORBA doesn't make sense right now. The
only thing we use MiG for in the Hurd is in the core interfaces.
Feel free to ask any *technical* questions on porting CORBA to the
Hurd on bug-hurd. Packaging issues are probably best discussed on
debian-hurd.
Mark
