WIP audio in server

[Andrei Kholodnyi]

Sorry, it was just a misleading comment from my side at the beginning of
this discussion.
What I meant is that audio shall be processed by the cleint part of the
speech dispatcher, not by the server itself.

It is a good option to propagate it to the cleints but only if client needs
it. E..g. it might be a cloud TTS server.

2016-02-14 3:48 GMT+01:00 Chris Brannon <chris at the-brannons.com>:

> Tim Cross <theophilusx at gmail.com> writes:
>
> > having played with writing a few speechd clients, I'm very glad I
> > don't have to worry about how to actually use/play the audio.
>
> Plus one, brother.  I'm a lazy programmer.  If I want to make my
> application talk, I probably don't want to have to handle the audio I/O
> on my own.
>
> > The sockets v pipes question is an interesting one
> *snip*
> > From a security perspective, pipes are probably a better
> > choice.
>
> Well, the default these days is to use Unix-domain sockets.  They're
> just files in the filesystem.  Access control is protected by standard
> filesystem permissions, which are well-understood.
> It's about as secure as pipes.
> You have to jump through some hoops to use actual Internet sockets with
> a recent Speech Dispatcher.
>
> -- Chris
>
> _______________________________________________
> Speechd mailing list
> Speechd at lists.freebsoft.org
> http://lists.freebsoft.org/mailman/listinfo/speechd
>



-- 
Believe is not enough, you must know
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20160214/466f23c0/attachment.html>