NPAPI:AsyncURLValues: Difference between revisions

Line 21: Line 21:
    
    
   NPN_AsyncGetValueForURL(NPP npp, NPNAsyncURLVariable variable, const char *url);
   NPN_AsyncGetValueForURL(NPP npp, NPNAsyncURLVariable variable, const char *url);
   NPP_AsyncReceiveValueForURL(char *value, uint32_t len);
   NPP_AsyncReceiveValueForURL(NPP npp, NPNAsyncURLVariable variable, const char *url, char *value, uint32_t len);


Every successful request (returning <code>NPERR_NO_ERROR</code>) should result in a single availability callback, with a NULL value if there was a problem coming up with a value. The callback can be nested (immediate, occurring prior to the return of the request call to <code>NPN_AsyncGetValueForURL</code>).
Every successful request (returning <code>NPERR_NO_ERROR</code>) should result in a single availability callback, with <code>value == NULL</code> if there was a problem coming up with a value. The callback can be nested (immediate, occurring prior to the return of the request call to <code>NPN_AsyncGetValueForURL</code>).


The plugin would be responsible for freeing any callback result via NPN_MemFree.
The plugin would be responsible for freeing any callback result via NPN_MemFree.
Confirmed users, Bureaucrats and Sysops emeriti
1,680

edits