Tobie Langel wrote:
So Tobie, how would you use the file protocol for an ajax request?
It's mainly a backwards compatibility issue (plus it can be useful for
testing purposes).
After some testing, I am seeing how using onNetworkError is not
helpful since some network errors (such as
So Tobie, how would you use the file protocol for an ajax request?
It's mainly a backwards compatibility issue (plus it can be useful for
testing purposes).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
I like the idea of having one handle for those cryptic error codes.
Would onNetworkError be different than onException ( does the
onException get called as well??)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hi Ken,
I didn't push the getStatus method further than that because there are
some issues with the file protocol in Safari (status is always equal
to 0 in that case if I remember well).
Proper support for the file protocol is something I'd like to have for
1.6 final.
It implies rewritting
jdalton wrote:
I like the idea of having one handle for those cryptic error codes.
Would onNetworkError be different than onException ( does the
onException get called as well??)
In my current implementation, a network error triggers onNetworkError,
onLoaded, onComplete, then onFailure.
