NPAPI:AsyncURLValues: Difference between revisions

Line 20: Line 20:
   } NPNAsyncURLVariable;
   } NPNAsyncURLVariable;
    
    
   NPN_AsyncGetValueForURL(NPP npp, NPNAsyncURLVariable variable, const char *url);
   NPError NPN_AsyncGetValueForURL(NPP instance, NPNAsyncURLVariable variable, const char *url);
   NPP_AsyncReceiveValueForURL(NPP npp, NPNAsyncURLVariable variable, const char *url, char *value, uint32_t len);
   void NPP_AsyncReceiveValueForURL(NPP instance, 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 <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>).
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>).
Confirmed users, Bureaucrats and Sysops emeriti
1,680

edits