KDE/kdeaccessibility/kttsd

[Andy Fawcett]

On Wednesday 21 September 2005 15:42, Dave Feustel wrote:
> On Wednesday 21 September 2005 07:18, Dirk Mueller wrote:
> > On Wednesday 21 September 2005 14:12, Gary Cramblitt wrote:
> > > Changing all the appId arguments to type QByteArray compiles and works,
> > > so I'm fine with that, if that is the decision.
> > >
> > > So, in general, has there been a decision to change all dcop arguments
> > > that used to be QCString to QByteArray, even if they are dcop appIds?
> >
> > No! it breaks on-the-wire protocol. Laurent, please stop breaking DCOP.
>
> Word is that DCOP disappears in KDE 4. If so, is breaking DCOP really a big
> issue?

Yes it is.

Until the replacement is in place, existing functionality and compatibility 
should be kept wherever possible. For some components, this is more critical 
than others. DCOP is one of these. In general, we should not break any form 
of communication protocol.

A.

-- 
Andy Fawcett                                     | andy at athame.co.uk
                                                 | tap at kde.org
"In an open world without walls and fences,      | tap at lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap at fruitsalad.org