[cups.general] Passing extra information from environmenttobackend?

[Erik Forsberg]

> As far as I understand it this cannot work because
> he is looking for a way that the same user is logged in
> several times at the same time and therefore any central
> place where an option setting is stored cannot work
> to distingush the sessions of this one user.

Correct.

> I.e. I wonder what the final purpose is why to distinguish
> between the sessions when all is done by the same user?

It's a thin client environment. Imagine a user that logs in from home,
running program A on a central server. He then takes his bike to work,
and runs program B, also on the server, but in a different session.

There's a feature for printing to a printer connected to the thin
terminal the user is using to access the thin client environment. 

It should not matter if the user is logged in from several physical
locations - printing to "thinlocal" (which is what we normally call the
queue, it's run by a backend we've written) should always make the
printjob appear at the terminal where the user is located when
submitting the print job. 

For this to work, we need to know the originating session id, to match
against the session database that tells us how to redirect the job.

Regards,
\EF

(Should you be interested, here's more information about the
printing features of the product:
http://www.cendio.com/products/thinlinc/features/printing)
-- 
Erik Forsberg                OpenSource-based Thin Client Technology
Systems Analyst/Developer    Phone: +46-13-21 46 00    
Cendio AB    	             Web: http://www.cendio.com