DCOM coming?

DCOM coming?

[Wessler, Siegfried]

Hello,

are there any plans to wrap DCOM ability into the Linux kernel "someday"? 
Or will you wait until .net might be widely acepted and don't go into DCOM
anyhow? 

Like it or not, but you need DCOM if you want to connect to DCOM organized
networks, like OPC and others.

I know about the Sourceforge freedce project, but that is still hanging and
I expect more capabilities and user comfort if a stronger group of
developers will take care and implement DCOM directly into the kernel like
Windoze somehow does.

There is a commercial DCOM solution available by Software AG, but that's far
beyond any GPL, but heavily expensive!

(This is just a question to get an idea about your planning, no complaining
at all!). 

Thank You.
Siegfried Wessler

Re: DCOM coming?

[Christian Neumair]

I think this is definitely no question to ask here.
Take a look at http://freedce.sourceforge.net/
or just go googling for +DCOM +linux

see you,
 Christian

RE: DCOM coming?

[John Hall]

On 21 May 2002 16:06 Wessler, Siegfried <Siegfried.Wessler@de.hbm.com>
wrote:

> If DCOM were wraped into the kernel, everyone could use it, as it
> would be a part of the os itself.

Something like DCOM does not belong in the kernel - it should be
implemented as a userspace library. The support in Microsoft Windows
AFAIK is implemented purely in userspace; Windows includes far more than
just a kernel.

Regards,
John

re: DCOM coming?

[Dan Kegel]

Siegfried wrote:
> [Let's put DCOM in the kernel.  That's the best way to make
>  sure it's universally available, isn't it?]

Putting stuff in the kernel is very dangerous; it's only done
if there's absolutely no other way.  Since DCOM is just 
a library for doing TCP/IP RPC, kinda, the only reason to put
it in the kernel would be speed.  (That's why RPC code is in
the kernel; the NFS kernel modules need it, and they really
do require maximal speed.)

Somebody *has* put something very similar to DCOM into the
kernel already; see http://korbit.sourceforge.net/
However, that was mostly done as an intellectual exercise;
nobody seriously uses it, and it's not in the main kernel.

Your basic assumption -- that putting DCOM in the kernel is
the best way to make sure it's available to everyone -- is
mistaken.  After all, the program '/bin/ls' is available to
everyone, and it's not in the kernel.  To make DCOM available
to everyone, just implement it as a good user-level library,
and people will pick it up as they need it.

If you want to help, there is a project implementing DCOM on Linux
at http://freedce.sourceforge.net/
Improving that project is the way to go; later, if performance
concerns merit it, you could consider doing whacky things
like moving it into the kernel.

Or you might consider convincing The Open Group to release
their DCOM on Unix compliance test suite as open source.
They'll do it for the right price, I'm pretty sure.
- Dan

Re: DCOM coming?

[Dominik Kubla]

On Tue, May 21, 2002 at 11:47:28AM +0200, Wessler, Siegfried wrote:
> Hello,
> 
> are there any plans to wrap DCOM ability into the Linux kernel "someday"? 
> Or will you wait until .net might be widely acepted and don't go into DCOM
> anyhow? 

Never. Either of it: that stuff belongs into user land.

> Like it or not, but you need DCOM if you want to connect to DCOM organized
> networks, like OPC and others.

So what? They are running on top of IP like everyone else.

Dominik Kubla
-- 
UFO is a SIG at the University of Mainz. Meetings are every odd monday of
the month in the workstation laboratory (Zentrum fuer Datenverarbeitung).
We are a Unix derivate independent group.  Every flavor of Unix is welcome.