KDE/kdeaccessibility/kttsd

[Gary Cramblitt]

On Wednesday 21 September 2005 05:44 pm, Michael Pyne wrote:
> On Wednesday 21 September 2005 17:16, Gary Cramblitt wrote:
> > I don't understand what you mean by "on-the-wire protocol".  Can you
> > elaborate?
>
> Basically the type of the parameters is only known by the applications
> (sending and receiving), and that is all that the DCOP server has to go on.
> Now, if you change the type of the parameter for the sender and don't do so
> for the receiver, the receiver will extract the data wrong.  The DCOP data
> is no longer binary compatible.

Ok, well yea sure! The thing is that all dcop apps that used to use QCString 
arguments have already had to change anyway (most to Q3CString because the 
conversion tool automatically did that).  But I'm assuming that we don't want 
to leave that solution in place permanently.  So the question becomes, what 
should they be changed to?  QByteArray?  DCOPCString (which currently doesn't 
work), or something else?

One thing I thought about doing. Change all the KSpeech QCString arguments to 
type KSpeechCString and typedef that to Q3CString for now.  When a decision 
is reached, change the typedef.  I haven't tried this, but I suspect it won't 
work because the dcop marshaling code won't know what KSpeechCString is.

I've also considered changing all the appId arguments to QString and avoid the 
whole problem.  Fortunately, the number of apps using KSpeech is pretty 
small, so this is doable.

-- 
Gary Cramblitt (aka PhantomsDad)
KDE Text-to-Speech Maintainer
http://accessibility.kde.org/developer/kttsd/index.php