Performs an AJAX DELETE request. Shortcut for a call to xhr with method set to 'DELETE'.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: data should be a plain object with only primitive types which are transformed into key/value pairs.

Performs an AJAX DELETE request. Shortcut for a call to xhr with method set to 'DELETE'.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: data should be a plain object with only primitive types which are transformed into key/value pairs.

Performs an AJAX DELETE request. Shortcut for a call to xhr with method set to 'DELETE'.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: data should be a plain object with only primitive types which are transformed into key/value pairs.

Performs an AJAX GET request. Shortcut for a call to xhr with method set to 'GET'. Additional parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Performs an AJAX GET request. Shortcut for a call to xhr with method set to 'GET'. Additional parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Performs an AJAX GET request. Shortcut for a call to xhr with method set to 'GET'. Additional parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Creates a <style> tag to load the CSS file at the given url.

Creates a <style> tag to load the CSS file at the given url.

Creates a <style> tag to load the CSS file at the given url.

Creates a <script> tag to load the script at the given url.

Creates a <script> tag to load the script at the given url.

Creates a <script> tag to load the script at the given url.

Performs an AJAX request with the POST HTTP method by default. When options.allfields is true, it will use the PUT-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server. 'body.action' has the value 'insert'

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'insert'. 'body.action' is the way to distinquish 'I.IO.insertObject' from 'I.IO.updateObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the POST-request: which is preferable if you don't know all the fields (like its unique id). if you send ALL the fields, set options.allfields=true. This will lead into using the PUT-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Performs an AJAX request with the POST HTTP method by default. When options.allfields is true, it will use the PUT-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server. 'body.action' has the value 'insert'

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'insert'. 'body.action' is the way to distinquish 'I.IO.insertObject' from 'I.IO.updateObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the POST-request: which is preferable if you don't know all the fields (like its unique id). if you send ALL the fields, set options.allfields=true. This will lead into using the PUT-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Performs an AJAX request with the POST HTTP method by default. When options.allfields is true, it will use the PUT-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server. 'body.action' has the value 'insert'

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'insert'. 'body.action' is the way to distinquish 'I.IO.insertObject' from 'I.IO.updateObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the POST-request: which is preferable if you don't know all the fields (like its unique id). if you send ALL the fields, set options.allfields=true. This will lead into using the PUT-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Creates a <style> tag to load the CSS file at the given url.

Creates a <style> tag to load the CSS file at the given url.

Creates a <style> tag to load the CSS file at the given url.

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Performs an AJAX request with the GET HTTP method and expects a JSON-object. The resolved Promise-callback returns an object (JSON-parsed serverresponse).

Additional request-parameters can be on the url (with questionmark), through params, or both.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: If you expect the server to response with data that consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects. Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/

Sends a HTTP request to the server and returns a Promise with an additional .abort() method to cancel the request. This method is the standard way of doing xhr-requests without processing streams.

Sends a HTTP request to the server and returns a Promise with an additional .abort() method to cancel the request. This method is the standard way of doing xhr-requests without processing streams.

Sends a HTTP request to the server and returns a Promise with an additional .abort() method to cancel the request. This method is the standard way of doing xhr-requests without processing streams.

Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note3: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note3: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2. The send data is an object which will be JSON-stringified before sending.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note2: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note3: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Sends a blob by using an AJAX PUT request. Additional parameters can be through the params argument.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Sends a blob by using an AJAX PUT request. Additional parameters can be through the params argument.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Sends a blob by using an AJAX PUT request. Additional parameters can be through the params argument.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note: params should be a plain object with only primitive types which are transformed into key/value pairs.

Sends data (object) which will be JSON-stringified before sending. Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'update'. 'body.action' is the way to distinquish 'I.IO.updateObject' from 'I.IO.insertObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Sends data (object) which will be JSON-stringified before sending. Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'update'. 'body.action' is the way to distinquish 'I.IO.updateObject' from 'I.IO.insertObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.

Sends data (object) which will be JSON-stringified before sending. Performs an AJAX request with the PUT HTTP method by default. When options.allfields is false, it will use the POST-method: see Note2.

The 'content-type' of the header is set to 'application/json', overruling manually options.

'data' is send as 'body.data' and should be JSON-parsed at the server.

The Promise gets fulfilled if the server responses with STATUS-CODE in the 200-range (excluded 204). It will be rejected if a timeout occurs (see options.timeout), or if xhr.abort() gets invoked.

Note1: The server needs to inspect the bodyparam: 'action', which always equals 'update'. 'body.action' is the way to distinquish 'I.IO.updateObject' from 'I.IO.insertObject'. On purpose, we didn't make this distinction through a custom CONTENT-HEADER, because that would lead into a more complicated CORS-setup (see Note3) Note2: By default this method uses the PUT-request: which is preferable is you send the WHOLE object. if you send part of the fields, set options.allfields=false. This will lead into using the POST-method. More about HTTP-methods: https://stormpath.com/blog/put-or-post/ Note3: CORS is supported, as long as the responseserver is set up to: a) has a response header which allows the clientdomain: header('Access-Control-Allow-Origin: http://www.some-site.com'); or header('Access-Control-Allow-Origin: *'); b) in cae you have set a custom HEADER (through 'options'), the responseserver MUST listen and respond to requests with the OPTION-method More info: allows to send to your domain: see http://remysharp.com/2011/04/21/getting-cors-working/ Note4: If the server response JSON-stringified data, the Promise resolves with a JS-Object. If you expect this object to consist of Date-properties, you should set options.parseJSONDate true. Parsing takes a bit longer, but it will generate trully Date-objects.