Inheritance diagram for burst.io.AbstractURIRequest:
Generally, a programmer need not use this directly, because the
bu_Runtime object has convenience functions such as
getDocumentAsync . If you want to get an instance of this abstract class that is supported by the current environment, us
To load and eval a script at a url from the same origin as this library, use instead
Several different implementation mechanisms are potentially available, according to the environment:
Regardless of mechanism, it is generally limited to loading data or script from the same origin as the library itself.
Some of the parameters that affect whether functionality is available include:
Public Member Functions
|void||getTextAsync (String url, Function handler, Boolean nocache)|
|Request the text content of the specified url, and call the handler when it arrives. |
|abstract void||getDocumentAsync (String url, Function handler)|
|Get a Document object from the specified url asynchronously. |
Protected Member Functions
|abstract void||getTextAsync_ (String url, Function handler)|
|The method the subclass must implement (AbstractURIRequest takes care of caching). |
Get a Document object from the specified url asynchronously.
This is implemented with HttpRequest if available, otherwise via a hidden iframe.
There is no return value. The handler function is called with the Document object as its firstu argument.
Request the text content of the specified url, and call the handler when it arrives.
If HttpRequest is available in the environment, that is used. Otherwise an iframe mechanism is used.
There is no return value. The handler is called with a first argument containing the text content. The second argument is the implementation-specific request object.
This function does not provide detailed control over such things as authentication, progress callback, and so on. For that, you would need to explicitly create an HttpRequest and use its methods directly.