URLAccess Stalls
URLAccess Stalls
- Subject: URLAccess Stalls
- From: email@hidden
- Date: Mon, 12 Dec 2005 14:49:45 -0700
Hi all, I have an http transfer library I have written that wraps
URLAccess so I can set cookies and headers as key/value pairs, handle
logging in with username and password with the keychain manager,
etc. I am pretty much done, except for the fact that URLAccess
stalls at random times! It is extremely frustrating to have
precisely what I need, but get blocked by this. I use URLOpen() to
read bits of data at a time. Sometimes my download just never
starts, the header is 4 bytes and contains CRLFCRLF, but the data
never comes. I tried calling URLIdle() and it was no help. I
noticed that if I call a separate URLDownload(), it "tickles"
URLAccess and my download starts. This is completely unacceptable,
because URLDownload() blocks. I guess I am SOL unless someone has
run into this before and knows how to fix it. I am hoping that this
is my fault and maybe I am calling URLGetPropertySize() or
URLGetDataAvailable() incorrectly, like maybe there is more data than
I think, or I need to do something to kick-start it. I have noticed
that it is sensitive to if I am running in the debugger, so I am
hoping I just fed it some uninitialized variables or messed up the
stack or something. Is this a known bug?
If I have to use CFHTTPStream, I guess that's what I'll do, but it is
scary how apple has adopted this policy of deprecating everything. I
worry what will happen with the switch to Intel. I'm not trying to
troll here, I just think that with the success apple has had lately,
they need to hire an expert in each deprecated API and write the
wrapper around their chosen tech, I mean, I can conceive of doing it
in a few weeks for URLAccess over CFHTTPStream, and even with a few
months of debugging, we are only talking thousands of $$$ here, not
millions. But you multiply that workload across hundreds of
developers, and these setbacks are really hurting us. I don't think
I am alone in feeling that way. And one thing I would like to see
is, if a bug is fixed, carry that change back through say 10.3
instead of only applying it to 10.4, or else developers are unable to
take advantage of the fixes. Just my two cents, thanx for your help,
P.S. Perhaps these deprecated APIs could be open sourced and apple
could fund the projects, for much less than doing it in-house. Heck
I would write the whole wrapper for a mere $10k (wink wink), with say
a 3 month commitment, since I may have to write something like this
anyway :-P
------------------------------------------------------------------------
Zack Morris Z Sculpt Entertainment This Space
email@hidden http://www.zsculpt.com For Rent
------------------------------------------------------------------------
If the doors of perception were cleansed, everything would appear to man
as it is, infinite. -William Blake, The Marriage of Heaven and Hell
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden