88
edits
Plugins:GenericHttpMethod: Difference between revisions
→Open Issues
| Line 78: | Line 78: | ||
== Open Issues == | == Open Issues == | ||
* 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?) | * 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? | * 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'' | ||
* 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? | * Do we need a way to abort a request? ''Yes. Return code from the notify callback, or new function?'' | ||
* Should we provide a utility method for extracting header values from the headers char*? ''We have discussed this on the mailing list, and there is strong consensus to keep access to the raw header information, but also support for providing a convenience method for parsing, potentially as open-sourced reference implementation though'' | * Should we provide a utility method for extracting header values from the headers char*? ''We have discussed this on the mailing list, and there is strong consensus to keep access to the raw header information, but also support for providing a convenience method for parsing, potentially as open-sourced reference implementation though'' | ||
* Should same-origin policy apply? If not, should the plugin be able to opt in? | |||
* Make it easier for plugins to follow a redirect? (creating a new request may be more work than it should be) | |||
* need to clarify encoding in filename and URL parameters (for old methods as well) | |||
* do we need to be able to specify a timeout? | |||