Session integration in Speech Dispatcher

[Luke Yelavich]

On Tue, Apr 13, 2010 at 09:41:42PM EST, Hynek Hanke wrote:
> 
> Hello,
> 
> I'd like to ask a few questions about commit
>   9f4bd2ef1f60d5b5be6885fa6a29c3e38e3f662a
> 
> ``More tightly integrate the server into a user session
> [...]
> When the user logs in, the SPEECHD_PORT environment variable is set
> to a unique port number, which is the base port set in intl/def.h, plus the
> user's UID.''
> 
> 1) How do we know that this port base+user_id, will be free to use
> for a given
> user_id? If not, what happens?

We don't, however I couldn't think of anything better at the time to ensure 
each user's speech-dispatcher instance didn't clash. There may also be a way 
one could check whether that port is in use, however scraping the output of 
netstat probably wouldn't have been the best solution.

> 2) How does this coexist with spd-conf? If not, should
> --enable-session-integration
> cause spd-conf not to be installed? Or should spd-conf be modified
> and left only
> for diagnosis, not settings?

My thoughts were that if session integration was used, spdconf shouldn't be 
needed, since things would be configured already for the user to get going.

> 3) I see the documentation is completely missing. This needs to be fixed
> before release.

Unfortunately I didn't get time to address documentation for these changes, so 
this is a fair call.

Luke