WARNING: THIS SITE IS NOW CLOSED: ONGOING WRITEUPS CAN BE FOUND IN THE SVN REPOSITORY USING LaTEX

Open Issues

• Separate HTTP specifics from document

Versioning

HTTP/1.1 202 Accepted
Server: occi-server/1.0 (linux) OCCI/1.0
Date: Wed, 27 Jan 2010 17:26:42 GMT
Location: /jobs/0098
Content-Length: 0

Complimenting the service-side behaviour of an OCCI implementation, a client MUST indicate to the OCCI service implementation the version it expects to interact with. For the clients, the information MUST be advertised in the request it issues. In the case of a HTTP Header Rendering, the client request should relay versioning information in the 'User-Agent' header. The 'User-Agent' field must include the same value (OCCI/X.Y) as specified for the Server HTTP header.

GET /jobs/0098 HTTP/1.1
Host: example.comAuthorization: Basic xxxxxxxxxxxxxxxxxxx
User-Agent: occi-client/1.0 (linux) libcurl/7.19.4 OCCI/1.0
Content-Length: 0

If a server receives a request from a client that supplies a version number higher than the service supports, the service MUST respond back to the client with an exception indicating that the requested version is not implemented. Where a client implements OCCI using a HTTP transport, the HTTP code 501, not implemented should be used.