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

List:       kde-core-devel
Subject:    Re: Speed of libDCOP was: Cool Helix startup [Fwd: K-ARTIST:Startup?]
From:       Harri Porten <porten () tu-harburg ! de>
Date:       2000-05-30 16:04:56
[Download RAW message or body]

Martin Konold wrote:

[ Wrong subject line. The speed of libDCOP is not in question. It's
certainly as fast as possible and fast enough for our needs. ]

> > > I serdoubt that you will gain significant speed but you definetely will
> > > increase the complexity while loosing maintainability.
> >
> > At least on my system the difference would certainly be noticable. It
> 
> Are you speculating or can you provide numbers? 

See the "symbol relocation" thread that came up on this list two weeks
ago. Michael and Waldo provided some detailed numbers.

> Beware that qtlib is most
> probably already in memory.

If I understood Rik's intention correctly he was looking for a way to
pop up a splash screen faster than any KDE app comes up. I'm not quite
sure why he's after DCOP communication but this can't - per definition -
be achieved with a KDE application itself ;)

> > would be a great way to start with plain C bindings, though. They are
> > definitely needed for interoperability with non-C++
> > applications/scripting languages that want to talk to KDE :)
> 
> C-Bindings can be indepentently provided while keep on using Qt for libDCOP.

Sure. Nobody was going to touch libDCOP. But nobody volunteered for
writing the bindings either. That's why Rik's work might be an "ignition
spark" for that task .

Harri.

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