Chris,
No idea why NSURLConnection is hanging on you. Actually, the
information here is incomplete so it might not even be
NSURLConnection. Attaching to the app in gdb and getting a stack
trace of all the active threads would be useful: 'thread apply all
bt' and 'info threads'. I suspect other things are going on since
this thread is wedged in __semwait_signal and unlikely to be the
culprit of 100% CPU utilization. The NSXMLStore is using Foundation's
NSXMLDocument which in turn is using NSURLConnection.
Filing a bug with bugreport.apple.com about the odd involvement of
cookies in a file:// URL would be best.
Reimplementing NSPersistentDocument yourself is not trivial.
NSDocument's API is pretty subtle, and it likes to play tricks on the
data files to implement features like auto save and safe save. If you
only have a tiny bit of code, then you're probably not conforming to
the joint expectations of NSDocument and Core Data.
NSPersistentDocument is not large, but neither is it tiny. There are
also nontrivial reasons why NSPersistentDocument does not yet support
file wrappers or auto-save.
You could also file an enhancement request for file wrapper support in
NSPersistentDocument.
- Ben
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
