Re: What happens to the AppKit Framework when an user logout ?
Re: What happens to the AppKit Framework when an user logout ?
- Subject: Re: What happens to the AppKit Framework when an user logout ?
- From: Georg Tuparev <email@hidden>
- Date: Wed, 17 Oct 2001 09:39:08 +0200
IMHO, what you describe below is the right behavior. Can you imagine the
mess if it was not so? In case no one is logged in, where are all events
going? Who (user) sends them? Have you thought about security issues?
If you would like to have service app, well no one stops you. Write a
Tool, and run it all the time. You can still use Foundation framework
for this. But you cannot use AppKit. If you must have UI, well, this is
also easy. Split your service app in server tool and UI client, and when
a user is logged in, let the client talk to the tool...
On Wednesday, October 17, 2001, at 03:13 AM, Will Price wrote:
In any case, everything works great until a user logs out. When a user
logs out, anything with a CFRunLoop appears to get killed. So far, we
haven't found a solution to this other than completely removing anything
that uses AppKit/Foundation from all background services which
effectively
renders useless the concept of Cocoa background services.
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196