Darren J Moffat wrote:
> For the sake of completeness can you explain why all the existing
> things don't meet needs and can't be enhanced to do so. Specifically
> I'm thinking of things like taskid and projid.
>
> [ I know we had this conversation before but I've forgotten some of it
> and I'd like it put in the public archives of this thread anyway ].
>
As for Sun Ray and audio:
Project IDs are probably not appropriate since they are (IIUC) a mostly
static thing. Sun Ray sessions come and go (very) dynamically, and this
doesn't seem to fit the model for Projects.
Tasks would almost work, I think, except that I fear that our use of
them might "conflict" with other uses. More specifically, if we use
taskids for this purpose, then Sun Ray users would be unable to use them
for other purposes without breaking audio for those applications in the
new task.
Its better, IMO, if we have a separate field, which is not overloaded
for other purposes, for this use. Environment variables would almost do
the trick as well, but there is no standard way for device drivers to
get environment variables from the u_area, and I do worry about the
tendency of software to clear their environment when spawning new
processes in the name of security.
No, its better if this new ID used for audio is *not* subject to being
cleared, changed, or inadvertently used, by either users or other software.
-- Garrett
