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

List:       kde-core-devel
Subject:    Re: app-start notification II
From:       Matthias Ettrich <ettrich () trolltech ! com>
Date:       2000-05-18 15:24:15
[Download RAW message or body]

Am Don, 18 Mai 2000 schrieb pbrown@redhat.com:
> On Thu, 18 May 2000, Rik Hemsley wrote:
> 
> > * It needs to link to libDCOP (not a problem) but also libqt, required
> >   by libDCOP. This slows down app start for non-qt-based apps as the
> >   symbols in libqt have to be resolved.
> 
> Maybe you could send a signal to the XMLRPC daemon and then you don't have
> to link DCOP or Qt.

All you really want to do is a DCOP send, right? It's trivial to extract the
necessary bits and pieces from libDCOP (dcopclient, to be precise) and make
them totally independent from Qt.

You only need attach(), not even registerAs(). The only remaining usage of Qt
is then in send() itself:

    QByteArray ba;
    QDataStream ds(ba, IO_WriteOnly);
    ds << d->appId << remApp << remObjId << normalizeFunctionSignature(remFun) << data.size();

doing this in ANSI C shouldn't be a problem. appId, remApp, etc. are QCStrings.
The marshalling format is simply the length of the string (as 32Bit integer)
followed by the string's raw data.

Matthias

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