| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Oct 19, 2005, at 5:40 PM, Mike Kluev wrote:
The question remains: was it just a documentation bug or did something in implementation change to make ReceiveNextEvent thread safe?
Speculation: "Carbon Events" consists of two halves. The lower half deals with eventRefs, eventQueues, eventLoops, eventTimers and corresponding APIs like CreateEvent, SetEventParameter, GetCurrentEventQueue, PostEventToQueue, ReceiveNextEvent, etc. Basically this is just wrappers above the corresponding CF stuff. The higher half is different; it introduces eventHandlers, eventTargets, event handlers' stack and corresponding APIs like GetFooEventTarget, InstallEventHandler, SendEventToEventTarget, CallNextEventHandler, etc. All the beauty of having events being automatically dispatched to appropriate targets is in the higher half. Lower half is thread safe or conditionally thread safe. Higher half is not thread safe (whom to blame for this? Ed? :-)
-eric
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/email@hidden
| References: | |
| >Re: Not thread safe events? (From: Mike Kluev <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.