Re: Fast User Switching in Panther...
Re: Fast User Switching in Panther...
- Subject: Re: Fast User Switching in Panther...
- From: David Remahl <email@hidden>
- Date: Fri, 1 Aug 2003 22:24:56 +0200
Well, the client application that wishes to use the services of the
server should then provide its username as part of the protocol. Each
application can get the UID of the user who's space it runs in using
getuid(). You then send that info to the server over TCP/IP.
Optionally, the server can authenticate the client by requiring a
password as well.
Doesn't that make sense?
Since applications not active in the current "FSU context" still run -
and can be controlled by AppleScripts, VNC, Timbuktu etc, it would not
be sufficient to check who is the owner of the current FSU context.
/ Rgds, David
On fredag 1 augusti 2003, at 22.20PM, Alec Carlson wrote:
David,
I'm using TCP/IP for both local and remote IPC.
Alec
on 8/1/03 3:09 PM, David Remahl at email@hidden wrote:
What IPC method are you using?
/ Rgds, David Remahl
On fredag 1 augusti 2003, at 21.32PM, Alec Carlson wrote:
I have a background app and a plug-in which runs as a subprocess of a
daemon. Both of these entities need to know who is making requests
for
their
services - the logged in user or the current (fast switched) user.
This
information is used to authenticate the user locally and remotely, to
access
the users preferences which are not kept in the
~user/Library/Preferences
folder because they need to be accessible when the user is not logged
in,
and to store files in user specific folders whether the user is
logged
in or
not. As such, both processes need to know who is making the request
so
that
when the request completes sometime in the future, the processes know
where
to put the results. Until Panther, you could only have one user
logged
in at
a time (ignoring the ssh case) and although you could have multiple
processes running as different users, those process couldn't interact
with
our GUI so they couldn't make service requests. A second user wanting
to use
their personal environment would have to logout the current user and
then
login as themselves. This reset the logged in userid so all was well.
So,
when a user makes a request for services, I need to know who they are
(at
that point in time). If someone else comes along and makes another
request I
don't care so long as I can tell the two users apart.
Alec
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.