[RFC] speech dispatcher client/server data types

[William Hubbs]

Hi Andrei,

On Mon, Oct 04, 2010 at 08:43:09AM -0500, Christopher Brannon wrote:
> 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, when you change a type in the client, you have to bump the shared
library revision number.

> Also, sharing declarations means that components of Speech Dispatcher
> could not be separated into subprojects, if the need ever arises.

The way to do this, imho, would be to copy the types from libspeechd.h
to some place in the include directory, but also leave them in
libspeechd.h so the API and server sides are not forced to share
the type declarations.  Sharing these type declarations is the thing I
am uncomfortable with about your proposal, not the actual data types.

William

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