Doc Maynard wrote:
NSUrl can be used to open a number of different connections to a number of different things. It is not a DNS Error as two computers configured the same do not respond the same. Whatever the case, the problem seems to be growing, not resolving. It will be curious to find out just what it actually proves to be.
http://developer.apple.com/library/ios/#documentation/Cocoa/Reference/Foundation /Classes/
NSURL_Class/Reference/Reference.html
Software Update works like it should again!
@Doc Maynard: at first, I responded to your message quoted above, that NSURLErrorDomain code 1100 was to mean that a file did not exist. That is a fact, and I can show the evidence for it now, by guiding you to the following link:
https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundatio n/Miscellaneous/Foundation_Constants/Reference/reference.html
If you'd then scroll down to URL Loading System Errors (about one third down), it reads:
These values are returned as the error code property of an
NSError
object with the domain “NSURLErrorDomain”.
You'll then see a number of possible values. If you search the list for value "-1100", you'll find it means NSURLErrorFileDoesNotExist. There you go. At least now you know where I'd got my information from.
The fact that this specific error was returned, could be because of SUAppStoreUpdateControler being unable to download the file it needed at that time from Apple's server.