RE: [FreeDCE-DCOMdev] DCOM/OPC implementation

[Wez F. <we...@th...>]

Hi Todd,

The DCOM part of FreeDCE still needs all of the in-process COM code as a
base, before it can be implemented fully.

A new project has very recently been set up on sourceforge, called OpenCOM
and we will be working with them to this end - but there is quite a way to
go.

This sounds like bad news for you, but you might be able to get away with
using the DCE only side of things, provided that you will only ever be
talking across a network with those devices, and that your Linux code will
only ever be a client.  If that sounds right for you, check out this
article: http://www.idevresource.com/com/library/articles/comonlinux.zip

Good luck!

--Wez.



>  Hi.
>
> I have recently begun working on a new project at work that
> involves writing
> OPC servers.  OPC (OLE for Process Control), is a specific set of COM/DCOM
> interfaces that are designed for inter-device communication for
> manufacturing systems.  The specs are available at
> http://www.opcfoundation.org.
>
> I've been programming for Linux for years, and am not looking forward to
> having to develop a large amount of software under Windows.  The
> majority of
> my team feels likewise.  However, the devices with which we have to
> communicate only seem to support OPC as an interface, and while we did
> discover there is a commercial product available that provides OPC
> functionality under Linux, it is not open source, requires
> runtime licensing
> fees, is only compatible with certain kernel versions, and has some other
> drawbacks.
>
> What we need is really an open source implementation of DCOM, and that led
> me to discover FreeDCE.  There haven't been any recent posts concerning
> DCOM, so I thought I would ask:  What is the current state of DCOM
> implementation in FreeDCE, and what can I do to help?
>
> _______________________________________________
> FreeDCE-DCOMdev mailing list
> Fre...@li...
> http://lists.sourceforge.net/lists/listinfo/freedce-dcomdev
>
>