Hello, > It would be great if you could re-use the ORBit2 infrastructure; for > many reasons: > > a) Code re-use, while marshalling is fairly trivial, there is a > great wealth of problems that you can hit, particularly: > * Interoperability - lots of subtlties here > * Profile management - fun stuff here too > * Socket communications - similarly > * Security ... etc. > > b) In-proc ABI, ORBit2 has an ABI that would let C bindings for > Mono objects not go through a complex Marshal to a socket, > de-marshal from a socket [ even in-proc ] process, but do > direct cross language calls, between eg. Guile, Python, > Mono, C
Although this would be useful, a pure managed implementation of CORBA would simplify the deployment of CORBA, and could get more people in the Microsoft world to use it. To make things even more interesting, if a .NET remoting CORBA binding is produced, it will allow people using Microsoft.NET to easily integrate with existing CORBA environments. Code reuse is really not that important to me for this particular case. For instance, just wrapping ORBit and mapping things to C# will be a lot of overhead. Miguel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
