From Open Siddur Project Development Wiki

Contents 1 Release 0.4.4 (Sept 2011) 1.1 Installation 1.2 Upgrade path 1.3 User interfaces 1.4 APIs

Release 0.4.4 (Sept 2011)

Release 0.4.4 is git commit f460ccfdbccd96627dfac13edd6a1d4b5e3c7c6e (tag v0.4.4).

The major new feature of v0.4.4 is the use of the background scheduling introduced in v0.4.3 to the TEI to XHTML compilation process. In previous versions, a user would be required to wait at a compile page while the server performed the compilation operations. In v0.4.4, the compilation is performed in the background on the server and the user is updated on the compilation status on their "My Siddurim" page.

Note: a bugfix release, v0.4.4.1 was issued for version 0.4.4 in Nov 2011. It maintains the same features as 0.4.4, except that a job control issue where a failed background job could cause the entire database to stop performing background jobs (issue#9) has been fixed.

Installation

Interested developers should follow the instructions at Building to download the source code from git. More information about how to read the source is being compiled at Intro to hacking.

You may also try the demo as a service at http://shell.jewishliturgy.org:8080/code/apps/builder

Upgrade path

• Because this is a tech demo release, no upgrade path will be provided. It is recommended that you uninstall, then reinstall the database.

User interfaces

Version 0.4.4 provides all the interfaces provided in version 0.4.3. In addition, the compilation page has been updated so it no longer involves a wait, and the My Siddurim page now displays the compilation status of the user's documents.

APIs

• The API discoverability has been improved. APIs now announce what methods they support and what MIME types they accept or return.
• APIs that accept parameters using HTTP POST are being moved to a new system where they will accept the more common application/x-www-form-urlencoded MIME type, in addition to text/plain, application/xml, text/xml and/or query parameters.
• The compilation API has been moved. Compilation is now initiated by a POST to /code/api/data/original/group/(user)/(resource)/compile
• A new status API has been introduced which allows a process to check on the status of a compilation. It is accessible through /code/api/data/output/group/(user)/(resource)/status