Paul:
Sorry for the delay in replying.
I agree that I'm violating my backward compatibility rule here. I've been thinking about it since this thread started and while I'm not respecting the async option setting, I'm not sure that I'll cause people problems.
Can you think of a legitimate case where someone would want to have a completefunc with async set to true? The only use case I can think of is where the code in the completefunc does something that has nothing at all to do with the Web Service call. That makes little sense, of course.
If async is true and there's code in the completefunc that is meant to process the result, it will only function properly sporadically.
The reason I ended up where I did is that async isn't valid with deferred objects, so I wanted to avoid using it if it wasn't valid.
Thanks,
M.
Sorry for the delay in replying.
I agree that I'm violating my backward compatibility rule here. I've been thinking about it since this thread started and while I'm not respecting the async option setting, I'm not sure that I'll cause people problems.
Can you think of a legitimate case where someone would want to have a completefunc with async set to true? The only use case I can think of is where the code in the completefunc does something that has nothing at all to do with the Web Service call. That makes little sense, of course.
If async is true and there's code in the completefunc that is meant to process the result, it will only function properly sporadically.
The reason I ended up where I did is that async isn't valid with deferred objects, so I wanted to avoid using it if it wasn't valid.
Thanks,
M.