[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC: #2 Separating audio output system for session integration

From: Halim Sahin
Subject: RFC: #2 Separating audio output system for session integration
Date: Thu, 26 Aug 2010 11:11:16 +0200

Hello all,

I had a little Conversation in pa list with Colin which was the reason
for me and Marco to think about the session integration stuff more

Now we came up with the following suggestion:
Seperate the whole audio output (sdaudio) from speech-dispatcher,
Run the speechd again in system mode and implement a small application
which connects to speechd gets the data for output and chooses according
to it's running session the right audiooutput method.
Colin called that application a speech-dispatcher-agent.

Marco has sugested a second socket for speechd where the communication
with the speech-dispatcher-agent can be handled.

doing this that way has many advantages:
Speechd can run as system, all screenreaders can use the same interface
to speechd.
Only the Audiooutput and the communication from s-d-a to speechd itself
needs to be implemented.

Not starting several processes for  speechd-server  or the screenreaders
would be needed!
Only the agent must take care of the sessionmanagement and it's primary
 work is to output the samples to right outputsystem!

 What do you think?
 @Hynek: Did you think in the same way or do you have a more useful

Speechd mailing list
Speechd at lists.freebsoft.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]