Batch Requests #177

Closed
titanous opened this Issue Mar 15, 2013 · 2 comments

Comments

Projects
None yet
2 participants
Owner

titanous commented Mar 15, 2013

Tent supports "Batch requests" via a POST to the batch endpoint.

A batch request is a series of HTTP requests nested inside of a multipart HTTP request. The requests are processed by the server, and a multipart HTTP response is returned with a series of nested HTTP responses. Each request must have its own Authorization header if the request needs to be authorized.

The order that the requests are processed in is not specified. The order that the responses are returned in is not specified. To identify a response, add a Content-ID header to the multipart headers of the request. Responses to requests with a Content-ID header will have a Content-ID header with the original value prefixed with the string response-.

These requests use the same format as Google Cloud Storage Batch Requests.

Contributor

quentez commented Apr 13, 2013

Google prefixes the Content-ID with response- instead of request-. Why the change?

Also, what Content-Type should we use? I've seen both multipart/mixed and multipart/batch.

Owner

titanous commented Apr 13, 2013

Google prefixes the Content-ID with response- instead of request-. Why the change?

Typo, fixed.

Also, what Content-Type should we use? I've seen both multipart/mixed and multipart/batch.

multipart/mixed.

titanous closed this Sep 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment