bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why GNU Mach is so different?


From: Farid Hajji
Subject: Re: Why GNU Mach is so different?
Date: Sat, 5 Jan 2002 13:27:06 +0100 (CET)

> > Regarding CORBA: The only part of it that we'll need in the Hurd
> > right now, is a good IDL stub generator that could replace MIG.
> > The path right now looks like we're needing to switch to flick
> > IDL compiler and change the *.defs with *.idl(s). Then, we could
> > use e.g. DICE or IDL4 to generate stubs for L4 instead of Mach.
> > Other CORBA stuff looks currently like unnecessary overhead to me.
> 
> Just my curiosity: Is it difficult to convert CORBA (or DCE) to MiG?
> 
> If that's easy, we could use (such a converter | mig) for Mach and
> IDL4 (or DICE) for L4...
The problem with MiG is that it does more than just marshalling and
unmarshelling the arguments and calling mach_trap(). I doubt that
using a mig2idl converter would solve our problems here.  IMHO, the
canonical way to do this is to switch to synch IPC completely (this is
probably even possible with mig) and take care of the few cases where
notifications/callbacks are needed. Once this is done, switching to
IDL (or any other interface definition language) would be quite easy.

I'm not 100% acquainted to the subtleties of MiG though, so please
take this with a grain of salt.

> Okuji

-- 
Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany  | farid.hajji@ob.kamp.net
- - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - -
One OS To Rule Them All And In The Darkness Bind Them... --Bill Gates.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]