iOS / asi-http-request

Conflicts:
	Classes/ASIHTTPRequest.m
	Mac.xcodeproj/project.pbxproj

* Request cache policies implemented as a bitmask - you can now combine multiple policies (eg: ASIAskServerIfModifiedWhenStaleCachePolicy|ASIFallbackToCacheIfLoadFailsCachePolicy)
* You can now tell requests to perform a conditional get only when the cached data is stale (if response is 403, new headers are written to the cache, but the existing response is preserved)

(Reported by Philippe Jayet)

Make clientCertificates work with NSCopying, headRequest, and release it in dealloc

Added a test for client certificates (iOS only)
Attempt to fix, YET AGAIN, building for 10.6 and that stupid NSXMLParserDelegate

Conflicts:
	.gitignore

Based on an idea from Jesse Rusak -> http://github.com/MindSea/asi-http-request/commit/f346f7f9de333501f732404323e8f73e911fbeea

…at it gets the name of the correct bundle, such as in the case of a Preference Pane.

… has been downloaded.

Tweak tests

Without this code, I found that adding assert(self.isCancelled) after [super cancel] resulting in the assert failing - ie. isCancelled was not returning true - when tested on an ipad running iOS 3.2.1 (not tested elsewhere).

…d are only sent at the point when finished is actually changed.

Also only send notifications for isExecuting if it has changed state. (markAsFinished can be called more than once for cancelled requests)

Cancellation ends up addressing runloop objects and CF objects (and also accesses the runloop for the current thread), at least some of which will only work on the thread the request is running on.

For example, cancel calls cancelLoad which calls destroyReadStream which needs to access the runloop for the request for this:

[[self readStream] removeFromRunLoop:[NSRunLoop currentRunLoop] forMode:[self runLoopMode]];

It seems that notifying the NSOperationQueue we're complete before we start running causes a problem resulting in a crash.

Hence, we avoid calling markAsFinished unless we're inprogress - main() will call it when we do start.

This can be used by clients to alter or inspect the queue.

The most obvious use for this is calling setMaxConcurrentOperations: on the queue to alter the number of simultaneous requests that will be made over the network.

Tweaks to fix more LLVM warnings