Re: cocoa-dev digest, Vol 1 #731 - 16 msgs
Re: cocoa-dev digest, Vol 1 #731 - 16 msgs
- Subject: Re: cocoa-dev digest, Vol 1 #731 - 16 msgs
- From: Jason Bobier <email@hidden>
- Date: Wed, 17 Oct 2001 12:04:42 -0700
The point is that you cannot use many parts of Foundation. Anything that
requires a runloop will be terminated. This means that DO (which we use
and is a fantastic way to provide services), timers, and various other
parts of Foundation are useless in a service.
Jason
On Wednesday, October 17, 2001, at 03:29 AM, cocoa-dev-
email@hidden wrote:
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...
--
Jason A. Bobier
email@hidden
Tech Lead, PGP Macintosh Products
http://www.prismatix.com/
Network Associates, Inc. Nothing's constant
PGPKey: <
http://keys.pgp.com:11371/pks/lookup?op=get&search=0xF6F83318>
Fingerprint: 7809 7E6E BCCA 903D 4618 9740 EB10 9DF9 F6F8 3318