[Mono-list] COM / DCOM in Mono
Eran Sandler
Eran.Sandler@smarteam.com
Sun, 2 Mar 2003 12:01:40 +0200
This is a multi-part message in MIME format.
------_=_NextPart_001_01C2E0A2.B83F5C64
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
As far as I know, the intentions of allowing Mono to run COM objects are
currently based around Wine.
I thought of something (Probably someone thought about it as well before
me, but I'll say it anyway) that might save us this trouble.
Why not treat all COM calls as DCOM. I know the performance will be VERY
bad compared toward in-process COM objects but that way, we can simply
put a Windows box near the UN*X/Linux one and call all the necessary COM
calls from it.=20
In this manner, we don't have to mimic all COM calls and the whole COM
layer, we simply delegate it back to where it works well enough.
What do you think about it?
Eran.
------_=_NextPart_001_01C2E0A2.B83F5C64
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.5762.3">
<TITLE>COM / DCOM in Mono</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Hi,</FONT></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">As far =
as I know, the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">intentions of allowing =
Mono to run COM objects are</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> currently based around Wine.</FONT></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">I thought of something (Probably someone thought =
about it as well before me, but I</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">’</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">ll say it anyway) that =
might save us this trouble.</FONT></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Why not =
treat all COM calls as DCOM.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">I know the performance will be VERY bad compared toward =
in-process COM objects but that way, we can simply put a Windows box =
near the UN*X/Linux one and call all the necessary COM calls from =
it.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
</SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">In this =
manner, we don</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">’</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">t have to mimic all COM calls and the whole COM layer, we =
simply delegate it back to where it works well enough.</FONT></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">What do =
you think about it?</FONT></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Eran.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>
</BODY>
</HTML>
------_=_NextPart_001_01C2E0A2.B83F5C64--