Author: buildbot
Date: Tue Nov 10 14:46:00 2015
New Revision: 971988
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 10 14:46:00 2015
@@ -1 +1 @@
-1713650
+1713651
Modified:
websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html
(original)
+++
websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html
Tue Nov 10 14:46:00 2015
@@ -115,7 +115,7 @@ This tutorial can be found in subdirecto
</ol>
<h1 id="1-introduction">1. Introduction<a class="headerlink"
href="#1-introduction" title="Permanent link">¶</a></h1>
<p>Batch requests <a
href="http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398359";>(OData
Version 4.0 Part 1: Protocol Plus Errata 02)</a> allow grouping multiple
operations into a single HTTP request payload. A batch request is represented
as a Multipart MIME v1.0 message <a
href="https://www.ietf.org/rfc/rfc2046.txt";>(RFC2046)</a>.
-Each part of a Multipart MINE message can have a differtent content type. For
example you can mix OData requests with Content-Type an
<code>application/json</code> and Media Ressource Requests with Content Type
<code>image/png</code>.</p>
+Each part of a Multipart MINE message can have a differtent content type. For
example you can mix OData requests with Content-Type
<code>application/json</code> and Media Ressource Requests with Content Type
<code>image/png</code>.</p>
<p>The content of batch requests can consist of a series of individual
requests and Change Sets, each represented as a distinct MIME part. In
difference to OData V2 an individual request can be a Data Request, Data
Modification Request, Action invocation request or a Function invocation
request. So all kinds of OData requests are allowed at top level. The order of
individual requests and Change Set sets in significant. Within a Change Set you
can use Data Modification requests and Action invocation requests. Due to the
fact that all requests within a Change Set are unordered, GET requests must not
be used within a Change Set. All operations in a change set represent a single
change unit so a service must successfully process and apply all the requests
in the change set or else apply none of them.</p>
<p><strong>Example</strong></p>
<p>The request below consists of a individual request (upper red box),
actually a GET request(the upper blue box) to the Entity Set
<code>Products</code> and a Change Set (lower red box). The Change Set contains
a single POST request (lower blue box) to create a new <code>Procuct</code>.
Please note that the <em>boundary delimiter</em> <code>abc123</code> is used in
the request below. The whole content must be wrapped in a single POST request
issued againest the resource <code>/$batch</code>. The Content-Type of the POST
request is consequently <code>Content-Type:
multipart/mixed;boundary=abc123</code></p>
