Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 03 Feb 2015 15:14:22 -0000
Message-ID: <20150203151422.88670.39710@eos.apache.org>
Subject: 
 =?utf-8?q?=5BJackrabbit_Wiki=5D_Update_of_=22frm/HttpOperations=22_by_frm?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" fo=
r change notification.

The "frm/HttpOperations" page has been changed by frm:
https://wiki.apache.org/jackrabbit/frm/HttpOperations?action=3Ddiff&rev1=3D=
3&rev2=3D4

  =3D=3D Read a revision =3D=3D
  =

  {{{
- POST /revisions
+ GET /revisions/last
  }}}
  =

- In case of success, the server returns a `201` response with a content ty=
pe of `application/json`. The body of the respnose is a JSON object, where =
the revision is the value of the `revision` property.
+ In case of success, the server returns a `200` response with a content ty=
pe of `application/json`. The body of the respnose is a JSON object, where =
the revision is the value of the `revision` property.
  =

  {{{
  {
@@ -51, +51 @@

  GET /revisions/:revision/tree/:path
  }}}
  =

- The `:revision` part of the URL is the revision that represents the state=
 of the repository used when reading. A value for this parameter is obtaine=
d by using a dedicated method of this API.
+ {{{
+ GET /revisions/last/tree/:path
+ }}}
+ =

+ The `:revision` part of the URL is the revision that represents the state=
 of the repository used when reading. A value for this parameter is obtaine=
d by using a dedicated method of this API. If the second kind of URL is use=
d, where `:revision` assumes the value of `last`, the read operation is per=
formed on the latest state of the repository known to the server.
  =

  The `:path` part of the URL is the path of the node in the repository tha=
t will be used as a root for the read operation.
  =

  Request parameters:
- =

-  * `revision` - the revision that represents the state of the repository =
used when reading. A value for this parameter is obtained by using a dedica=
ted method of this API. This parameter is mandatory and is a single-value p=
arameter.
  =

   * `depth` - the maximum depth of the tree returned by the response. This=
 parameter is optional and is a single-value parameter.
  =

@@ -111, +113 @@

  PATCH /revisions/:revision/tree
  }}}
  =

- The `:revision` part of the URL specifies the revision the patch should b=
e applied to. A value for this parameter is obtained by using a dedicated m=
ethod of this API.
+ {{{
+ PATCH /revisions/last/tree
+ }}}
+ =

+ The `:revision` part of the URL specifies the revision the patch should b=
e applied to. A value for this parameter is obtained by using a dedicated m=
ethod of this API. If the second kind of URL is used, where `:revision` ass=
umes the value of `last`, the patch operation is performed on the latest st=
ate of the repository known to the server.
  =

  The request must have a content type of `application/json` and its body m=
ust contain the set of operations to apply to the content represented accor=
ding to the following rules.
  =

@@ -172, +178 @@

  =3D=3D Read a binary object =3D=3D
  =

  {{{
- GET /revisions/:revison/binaries/:binaryId
+ GET /binaries/:binaryId
  }}}
  =

  If the binary object represented by `:binaryId` is found, the server retu=
rns a 200 response with a content type of `application/octet-stream`. The r=
esponse body contains the whole content of the binary object.
@@ -187, +193 @@

  =

   * if two or more ranges are requested by the client, the server returns =
a 206 response with a content type of `multipart/byteranges`. The response =
contains a multipart body, where each part represents one range as requeste=
d by the client. Every part has a content type of `application/octet-stream=
` and a `Content-Range` specifying which portion of the binary object the r=
ange represents.
  =

+ More detailed information about range requests can be found in RFC7233. =

+ =

  =3D=3D Write a binary object =3D=3D
  =

  {{{
- POST /revisions/:revision/binaries
+ POST /binaries
  }}}
  =

  The request should have a content type of `application/octet-stream`. The=
 payload of the request will be saved by the repository in a binary object.