__MPConnectionActiveList unnecessary and perhaps requestRuns mechanism too

[smallduck]

The MPConnection class seems more complicated than it needs to be. __MPConnectionActiveList seems to serve no purpose, was it intended to ensure the object was not released while the NSURLConnection was working? If so, then it's unnecessary because NSURLConnection is documented to retain its delegate.

It seems also that requestRuns is also unnecessary if you require that the caller doesn't fire off multiple simultaneous requests with the same MPConnection object, which seems reasonable since it's just as easy to make multiple MPConnection objects. Instead of a requestRuns dict, each would have simple members for the single set of NSURLConnection, NSInvocation and userData

[mattpat]

I'll agree with you on half of this: __MPConnectionActiveList is indeed technically unnecessary, though I haven't decided yet whether I want to change it; the additional overhead required is so minimal that the extra safety net (in case NSURLConnection changes its behavior, since non-retained delegates are far more commonplace) may be worth it. We'll see, though. :)

As for requestRuns, it does exist so that the caller can fire off multiple simultaneous requests with the same MPConnection. I can see a number of instances where this could be useful, if only from a syntactic perspective, and while I doubt it's a common use case, I'm going to leave the structure the way it is so that this method of operation is supported.

Thanks!