[Mono-devel-list] Re: un-interoperatible classes .NET -> Mono

Richard Norman normri at samc.com
Thu Sep 30 18:46:38 EDT 2004

I am just reposting this because I forgot the cardinal rule... "Change
the Subject to something meaningful..."
So I am just resending with the proper subject.
<PreviousPost type="Silly XML Style">
Just a quick comment on this from me (I try to follow Don Box's
in this world closely). I agree 100%. Remoting should be limited to
interappdomain/process communication. The recommenced path (according
Microsoft) is to use ASMX primarily, or if higher performance is
use DCOM I believe. Remoting was reserved for communication between
processes where types can be "guaranteed" to be the same.
Also with Indigo they are going toward the "WSE" style of
interoperability. So instead of using a "remoting" style of interop,
they are using the ASMX style of connected systems where the contracts
are shared but not the types. I would recommend in Mono an investment
made WSE classes as they would be a precursor to Indigo classes
in Mono. I know it will take some effort creating the channels and
and so on, but I think it would be a step in the right direction.

According to some of the quotes I've read, remoting is in a similar
state as COM.. It is not dead, but it is pretty much done. Most
development will be in the WSE style of coding and connecting.

Anyway, that's my 2 cents on the issue.


Richard Norman
Jazzynupe at sbcglobal.net 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20040930/47301940/attachment.html 

More information about the Mono-devel-list mailing list