[RFC] speech dispatcher client/server data types

[Christopher Brannon]

Andrei Kholodnyi <andrei.kholodnyi at gmail.com> writes:

> My proposal would be to align these data types
> and use the data types definitions from the libspeechd across all
> project modules
> with a clear advantage of consistency in data types between client and server.

We have a trade-off.
I can see the advantage: consistency.
The disadvantage is coupling.  If someone ever needs to change one of
those shared types, it must change in both the client and server, even
if there's a good reason for changing it in only one component.
Also, sharing declarations means that components of Speech Dispatcher
could not be separated into subprojects, if the need ever arises.
Those are the arguments against your proposal, as I see them.  Honestly,
I don't have very strong feelings either way, so I'm curious to see what
others have to say.

-- Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20101004/90128a1d/attachment.pgp>