Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to version 1.2.1 #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update to version 1.2.1 #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions specification.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@


<h1>Woopsa Protocol Specifications</h1>
<p>Version 1.2 &mdash; 12.08.2016</p>
<p>Version 1.2.1 &mdash; 02.03.2022</p>

<h2>Table of contents</h2>
<div id="table-of-contents">
Expand Down Expand Up @@ -114,7 +114,7 @@ <h3 id="transport">Transport</h3>
<p><samp>http://{server-address}/{route-prefix}/{woopsa-verb}/{woopsa-path}</samp></p>

<p>When the client has no data to send to the server (<samp>read</samp> and <samp>meta</samp>), requests are made using <samp>GET</samp> and the URL is the only piece of information needed by the server.</p>
<p>When the client has data to send to the server (<samp>write</samp> and <samp>invoke</samp>), requests are made using <samp>POST</samp> and the HTTP <samp>Content-Type</samp> must be <samp>application/x-www-form-urlencoded</samp>. Form data must be represented the way it would be if it were JSON-serialized. This means, for example, that numbers need to use a "dot" (.) as the decimal separator, and must not have any thousand separators.</p>
<p>When the client has data to send to the server (<samp>write</samp> and <samp>invoke</samp>), requests are made using <samp>POST</samp> and the HTTP <samp>Content-Type</samp> must be <samp>application/x-www-form-urlencoded</samp> or <samp>application/json</samp>. In case of <samp>application/x-www-form-urlencoded</samp>, form data must be represented the way it would be if it were JSON-serialized. This means, for example, that numbers need to use a "dot" (.) as the decimal separator, and must not have any thousand separators.</p>

<p>The Woopsa path is represented as a standard HTTP path URI. The path separator is thus also the <samp>/</samp> character.</p>

Expand Down Expand Up @@ -412,4 +412,4 @@ <h4><samp>MultiRequest(JsonData Requests) : JsonData</samp></h4>
For methods returning void, "Result" contains the value null.
</dd>
</dl>
<p><strong>Note:</strong> It is the role of the client to ensure the <samp>Id</samp>s are unique. The server should not try to do this verification.</p>
<p><strong>Note:</strong> It is the role of the client to ensure the <samp>Id</samp>s are unique. The server should not try to do this verification.</p>