Platform Release 13 Notes
From n² wiki
[edit] Content Length Header No Longer Returned
This release includes some performance and scalability work which means that responses are streamed out to the calling client and not read into memory. This means that the length of the response is not known before the response is written. As a consequence we are no longer returning a content length header in responses.
[edit] API-101 - Describe Service
This service makes RDF descriptions of resources addressable via HTTP. The descriptions can be fetched, updated and deleted using standard HTTP verbs. All HTTP accessible graphs in the Platform should support this behaviour.
The URI of the resource being described is supplied using a new query parameter: "about"
For example:
http://api.talis.com/stores/mystore/meta?about=http://example.com/foo
The about parameter takes a single URI as a value. This URI identifies a "description" of the resource containing all the RDF triples that have the resource as their subject.
Conditional GETs are supported so clients can ask for descriptions to only be sent if they are different to the one the client saw last time. This can enable clients to cache descriptions efficiently and so save on bandwith and processing.
Content negotiation on GETs are supported and controllable via an "output" parameter so the user can obtain the descriptions in rdf/xml, turtle, ntriples and XHTML.
A GET on the URI of the graph can respond with an XHTML document containing a form allowing a user to manually enter the query parameters (like the form on /items or /services/facet).
[edit] Other Bug Fixes
Other bug fixes in this release include:
- http://jira.talis.com/browse/API-127 - DELETE on content item already deleted returns 500 but should return 410
- http://jira.talis.com/browse/CAL-669 - Lease on Config lock tuple may be too short in Configuration update coordinator

