Re: ORBit status?

[Miguel de Icaza <miguel nuclecu unam mx>]

> - A robust binary interface specification for object implementations
> contained in shared libraries. A kind of in-process equivalent to
> GIOP/IIOP.

CORBA supports this already.  ORBit should support it as well.

> - Given the above, a client stub can just be a shared library
> containing an object implementation which happens to convert method
> calls into on-the-wire GIOP requests, just as DCOM/DSOM do it.

Look in the design specs for ORBit.  At least there used to be a small
design document that explained how this would work.

> - Support for asynchronous object requests, i.e. the out parameters
> and return value of a method call get passed to the client using a
> callback. 

Also supported by CORBA.  Look for "oneway" in the IDL description.

> - Extended language bindings for C. The CORBA C language binding is
> pretty awful, compared to Gtk-style object-oriented C. 

The bindings and style share a lot.  Exactly which parts did you
dislike?

Miguel.