88
edits
Plugins:GenericHttpMethod: Difference between revisions
→Open Issues
| Line 79: | Line 79: | ||
* Do we need a separate callback for the final state (as in NPN_PostURLNotify, or should we just keep calling NPP_HttpResponseNotify and add a status field as in XmlHttpRequest?) ''This may be obvious from the calling sequence, but we certainly need to clarify and add examples'' | * Do we need a separate callback for the final state (as in NPN_PostURLNotify, or should we just keep calling NPP_HttpResponseNotify and add a status field as in XmlHttpRequest?) ''This may be obvious from the calling sequence, but we certainly need to clarify and add examples'' | ||
* Is there a better way to pass in flags than setting bits in an integer parameter? ''Seems to be an acceptable approach; need to be clear what the defaults are though'' | * Is there a better way to pass in flags than setting bits in an integer parameter? ''Seems to be an acceptable approach; need to be clear about what the defaults are though'' | ||
* Error handling in XHR (due to historical reasons) is a weird mix involving readyState, httpResponseState (going back to 0) and exceptions; we should do better than that. | * Error handling in XHR (due to historical reasons) is a weird mix involving readyState, httpResponseState (going back to 0) and exceptions; we should do better than that. | ||
* Do we need a way to abort a request? ''Yes. Return code from the notify callback, or new function?'' | * Do we need a way to abort a request? ''Yes. Return code from the notify callback, or new function?'' | ||