[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: RPC Mechanisms (was: Re: [PATCH] bug in latest cvs
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-09-25 17:48:55
Message-ID: 200409251748.55877.frans.englich () telia ! com
[Download RAW message or body]

On Saturday 25 September 2004 16:02, Cornelius Schumacher wrote:
> On Saturday 25 September 2004 12:59, Luke Kenneth Casson Leighton wrote:
> > DCE is one of the most... unbelievably comprehensive bits
> > of engineering i have ever come across - and that's just the
> > runtime environment (let alone the projects that then used it,
> > such as DCE/DFS).
>
> Do you have some pointers where can be found more information about the
> unbelievable compresehensiveness of DCE/RPC?
>
> > DBUS is about as close to the shit mechanism "XML-RPC" as you can
> > get, in fact it is WORSE.
>
> What's the problem with XML-RPC?
>
> > you should be aware that, at some point in time, time and
> > money permitting, i plan to do a complete and total coversion
> > of all KDE source code to use DCE/RPC instead of DCOP.  irrespective
> > of whether anyone actually "likes" it.
>
> I'm looking forward to this. This will be interesting. In fact, if KDE
> programs would more extensively use the dcopidl compiler, replacing the
> RPC machanism would be fairly simple. 

> It could boild down to write 
> another output backend for dcopidl (by the way, this would be a really
> simple way to port DCOP to Windows, adjust the dcopidl compiler to
> generate code that uses an RPC mechanism which is easily available
> under Windows, whatever that might be).

I once wrote an IPC mechanism using the Windows messaging system. Now I'm into 
open source.


			Frans



 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]