Erik is correct, you would absolutely want to use Remoting, not WS's
for performance reasons. At my last job I tested this extensively as
we had COM server objects in VB6 that we didn't have time or resources
to port. The WebServices avenue was prettier and easier to deploy, but
was significantly slower and more vulnerable to scalability issues.
Andy
On Jan 4, 2005, at 9:33 AM, Erik Dasque wrote:
On Jan 4, 2005, at 7:16 AM, Jonathan Pryor wrote:
There is an alternate approach, though: Leave your COM code on
Windows,
and write a .NET front-end which uses .NET COM Interop to use your COM
objects. The front-end could be an XML Web Service or a
System.Runtime.Remoting server, both of which Mono can communicate
with.
Thus you'd have:
Mono/Linux --> [Network] --> .NET Web Service --> COM Component
This is likely the easiest approach, though its performance won't be
spectacular.
- Jon
Yes, I think that's the best option though you might want to use
remoting instead of WS in that case.
Erik
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
