on 06/11/10 23:15, Paul Haddad at email@hidden wrote:
I'm not sure if that memory usage is excessive, but I have seen that
NSURLConnection does seem to leave things hanging and have filed a bug or
two. Search the archives and you'll find several interesting stories.
Well it seems pretty excessive to me in general (though may just be
what NSURLConnection uses).
I switched my code out to use CFHTTPStream instead which by comparison
uses almost no resources and doesn't even spawn a thread (or if it
does it goes away after its done). The only thing it seems to keep
hanging around is ~600-700K worth of SSL data which isn't optimal but
not anywhere near as huge a deal.
IMO unless you do a ton of HTTP requests I think NSURLConnection is
best avoided, NSURLHandle and CFHTTPStream seem to be much better
choices.
--
Paul Haddad (email@hidden email@hidden)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
