KDE/kdeaccessibility/kttsd

[Michael Pyne]

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.

Basically, it's like changing this:

void callFunction(const char *str);

void foo()
{
  callFunction("bar");
}

to this:

void callFunction(const char *str);

void foo()
{
  QString str("bar");
  callFunction((const char *) &str);
}

The DCOP server doesn't realize it's passing erroneous data and who knows what 
could happen after that. =D

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050921/4698d658/attachment.sig>