[Fwd: [Fwd: PSARC 2008/043 Phase 1 of OSS for Solaris]]

[Michael Bender/MBP]

Nicolas Williams wrote:
> On Wed, Jan 23, 2008 at 01:44:19PM -0800, Dev Mazumdar wrote:
>> There is a sound server process for each client. The server process 
>> opens the server side device of audioloop. The audioloop driver creates 
>> a new device instance (client/server device pair) and binds it to the 
>> UID of the user (I assume they use UID to identify the sessions).
>
> So if I have multiple sessions on the same server then one session will
> get all the sound for all of them while the others get no sound?

We use a session ID that is unique to the Sun Ray server that the
session is running on. That session ID is not related to the UID
of the user that has logged in to the Sun Ray server via a DTU,
although once a user has logged in their UID and session ID are
bound for the duration of the user's session.

>> The main problem is to make OSS to scale to up to 100k clients without 
>> using all available memory. It will also take some time to get OSS to 
>> use UID or some other client identification to redirect access to the 
>> right server.
>
> "some other client identification" seems like a better answer than "UID."

Yes, I agree.

mike