RAWS Release Notes
Contents |
Current Versions
See below for an overview of the changes and possible backward-compatibility issues.
See the roadmap for information about future releases.
META
version 3.60
April 1, 2012.
- New service with enhanced metadata support
- Full supports for the JSON data format
- For details, see the META API
RAMS
version 3.60
April 1, 2012.
- resource lists in JSON
No backward-compatibility issues.
version 3.30
March 23, 2011.
- Traffic resource extended with support for metadata queries
No backward-compatibility issues.
version 3.20
November 1, 2010.
Contains:
- New user resources: total, geo, concurrent and traffic-type.
- New customer resources: users, payed and used.
- User behaviour data added to the traffic resource.
- Support for ATOM pagination. Results for a single request defaults to 50 when using RAMS v3 resources or features.
- Additional traffic types: "rtmp_live", "rtsp_live", "smooth" + "smooth_live" (Silverlight streaming), "cupertino" + "cupertino_live" (iPhone HTTP streaming), "sanjose" + "sanjose_live" (Flash HTTP streaming), "rams", "rase".
- Date ranges can be used as query-string arguments for 'traffic', 'concurrent', 'used' and 'payed' resources.
- The kind query-string argument can be used in 'traffic' requests (when using RAMS v3 features, the traffic resource only returns a single kind).
- Support for recursive 'traffic' requests (by passing "kind=recursive" in the query-string).
- Support for HTTPS requests (optional).
- Added ping resource
Backward Compatibility
All API changes are backward compatible, with exception of the one(s) mentioned below:
- A single 'traffic' request can no longer span multiple years when using RAMS_time_units.
- "misc" is no longer used as a value for the 'raws::kind' attribute: unresolved URLs now have their 'kind' attribute set to "file".
For backward compatibility reasons, some limitations (required pagination, single 'kind' in response) only apply to the 'traffic' resource when a request uses RAMS v3 features (= by using query-string arguments that didn't exist in RAMS v2).
Announcement: backward incompatible changes for RAMS 4.00
RAMS v 4.00 will impose pagination for all requests and will no longer allow the "all" value for the 'kind' query-string argument. See the 'traffic' page for more details.
version 1.80
December 13, 2009.
Bugfix release with some minor additional features.
version 1.40
December 11, 2008.
Contains additional time-units for RAMS traffic resource: week, day, hour. No backward-compatibility issues.
RATS
version 3.60
April 1, 2012.
- support of automatic metadata creation
- enhanced CDN reports
- post-procs in JSON
- resource lists in JSON
No backward-compatibility issues.
version 3.50
Februari 17, 2012.
- support for a large number of additional source file formats, including Apple's ProRes video codec, Bink video, WMA Pro, WMA Voice...
- faster decoding and encoding
- added functionality to API for batch jobs (snapshots, custom actions, protocols)
- additional data included in CDN report
- if metadata is enabled, RATS will send a POST request to the RASS related resource
No backward-compatibility issues.
version 3.40
May 27, 2011.
- official WebM support (use the default webm format with ID=9, or create your own) + improved Ogg encoding
- ability for users to securely (https) set credentials on input and output profiles
- ability to run jobs for groups of formats (single job / multiple formats)
- framework for automation of adaptive streaming
- (backward incompatible) change to the overlay resource (see below)
Backward Compatibility
The mode and threshold params of the overlay resource have been replaced by the single position param. See the resource page for more details.
version 3.30
March 23, 2011.
- Improved source format handling
- Debugging in the browser allowed over https
No backward-compatibility issues.
version 3.20
November 1, 2010.
Bugfix release with some minor additional features (support for https requests, upon request).
version 3.00
April 7, 2010.
Contains:
- Improved upload handling, interlinking, web interface
- Invalid filenames (= not according to Rambla conventions) in the SLUG header are renamed automatically by RAWS.
- Support for dedicated transcoding daemons, upon request
- Support for device-specific (e.g. 'iPhone') encodings: device param added to format profiles
- Added ping resource
Backward Compatibility
All API changes are backward compatible, with exception of the one(s) mentioned below:
- File uploads that contain an invalid filename in the SLUG header will now succeed and return the correct filename in the response. Previously, the upload would fail and return an error response.
version 1.80
December 13, 2009. Bugfix release with some minor additional features.
version 1.60
June 12, 2009. Contains:
- New formatgroup and batch functionality. Note that this functionality is not part of the API; it can only be used through the RATS site.
- Improved source file detection.
- Better load balancing
No backward-compatibility issues.
version 1.50
January 23, 2009.
Additional features for the job resource:
- A proc param has been added to the job resource's content. This allows the client to request RATS to perform additional actions while processing a certain job.
- The video_height and video_width params have been added to the job resource's content. When these params are set in the job request, they override the 'video_height' and 'video_width' settings of the format profile.
- Includes the possibility to filter a list of job resources using a string that is part of the client_passthru param. This allows the client to group his jobs easily, e.g. based on the end-user for which the transcoding is being done.
No backward-compatibility issues.
version 1.40
December 20, 2008.
Contains:
- Bundle of API feature requests
- Transcoding engine improvements
- Cloud infrastructure, supporting Load Balancing and High Availability
API extensions
- The 'import_location' param has been added to the job resource; it should be used when referring to a source file that needs to be imported from a remote location by RATS. After RATS has completed an import operation, it returns the new src filename via the 'src_location' param of the job resource instance or via the 'src_location' element in the import section of the job report.
- The value of the 'startpos' param of the job resource may now also be a percentage (= number followed by a % sign, e.g. '20%'). This is very useful when taking snapshots.
- The 'video_bitrate' and 'audio_bitrate' params have been added to the job resource's content. When these params are set in the job request, they override the 'video_bitrate' and 'audio_bitrate' settings of the format profile.
- Includes the possibility to filter a list of format resources by container or container type.
- Rambla can define default 'input', 'output' or 'format' resources, which can be used by all customers. The 'owner' query-string argument may be used to include these default profiles in a profile list.
- A 'size' param has been added to the 'src', 'transc' and 'overlay' resources, specifying the filesize in bytes.
- Support for unicode in "free-text" properties.
Backward Compatibility
All API changes are backward compatible, with exception of the one(s) mentioned below:
- The 'allow_overwrite' is removed from the output resource params. If an export operation refers to a filename that already exists on the remote host, RATS will NOT overwrite it. Instead, RATS will try to complete the export operation by adding a suffix to the filename that needs to be exported. The final export destination can be retrieved through the job report's 'export_uri' and 'public_uri' elements.
Since the 'import_location' param is now available, this should preferably be used when referring to a source file that still needs to be imported. For backward compatibility, the 'src_location' param in a POST job request may also still be used. However, such usage of the 'src_location' param is deprecated, and will be removed in the next major RATS upgrade!!
version 1.20
November 20, 2008.
Encoding engine improvements added + job report extended with new elements.
RASS
version 3.60
April 1, 2012.
- metadata support migrated to the META service
- resource lists in JSON
No backward-compatibility issues.
version 3.50
Februari 17, 2012.
- Overall improvements to the metadata resources (see wiki)
- 'lang' attribute added to the meta element, 'meta' attribute changed to 'meta_name'
- New 'lang' query-string argument for the RASS meta resource
- New RASS related resource, allowing videos with the same content to share metadata
version 3.30
March 23, 2011.
- Support for metadata (see the technical overview and getting started guide for more info), which includes:
- Support for searches by file and directory name for the dir, ext and meta resources
- Improved pagination and formatting of ATOM link elements
No backward-compatibility issues.
version 3.20
November 1, 2010.
- Support for the atom:link element with a "last" relationship by 'dir' feeds, for requests that pass a single value in the 'kind' query-string argument.
- Support for https requests, upon request.
No backward-compatibility issues.
Announcement: backward incompatible changes for RASS 4.00
RASS v 4.00 will start to impose pagination for all requests. See the 'dir' page for more details.
version 3.00
May 17, 2010.
- Support for ATOM partial lists for the dir and meta resources
- Added new itemdata resource method that can be used to retrieve the entry corresponding to an existing item.
- The HTTP POST method is supported by the dir resource. This method makes sure that the directory is being created, even if a directory with the same name already exists (= RASS will append a numerical suffix to the proposed filename).
- PUT dir will also create parent directory that are required for creating a sub-directory.
- Support for recursively deleting directories.
- ATOM entries representing a file on the CDN contain an 'atom:link' element with an enclosure relationship and an 'href' attribute that points to the item's CDN location (=URL).
- Invalid filenames (= not according to Rambla conventions) in the SLUG header of a POST item request are renamed automatically.
- Extended meta resource.
- Added ping resource.
Backward Compatibility
All API changes are backward compatible, with exception of the one(s) mentioned below:
- When POSTing or PUTting a item resource, the response's "Location header" will point to the item entry that has been created (= GET itemdata) instead of to the file's download location (= GET item).
- Enclosure URL inside item (file) entries will refer to the location of the file on the CDN (<-> RASS item location).
version 1.80
December 13, 2009.
Bugfix release with some minor additional features.
version 1.40
January 23, 2009.
New in this release:
- support for enclosure links : atom entries that describe a binary file now have an extra link with the enclosure relationship type (rel="enclosure"), while the alternate link now points to an entry with the metadata for this file.
- HTTP POST method now supported for the item resource. This allows for "assured file creation": POST item will result in the uploaded file to be created by RASS, even if the path doesn't exist (RASS will first create the directories) or if a file with the same name already exists (RASS will append a numerical suffix to the proposed filename).
- A new meta resource has been created for future use (e.g. retrieve multimedia properties, tagging...). Currently, it can already be used for getting general filesystem metadata (for both files and directories).
No backward-compatibility issues.
version 1.20
May 6, 2008.
RASS is now using the RAWS framework, including APP and ATOM support.
RASE
version 3.60
April 1, 2012.
- resource lists in JSON
No backward-compatibility issues.
version 3.50
Februari 17, 2012.
- Extended the wowapp resource to return more info about broadcast/stream
- Users can (re)set their password for retrieving number of concurrent live viewers
No backward-compatibility issues.
version 3.30
March 23, 2011.
- Debugging in the browser allowed using https
No backward-compatibility issues.
version 3.20
November 1, 2010.
Bugfix release with some minor additional features (support for https requests, upon request).
version 3.00
April 9, 2010.
Contains:
- New sniff resource
- Auto-cleanup of unbound ports
- Warning mails being sent to the user when his port limit is near (at least 70% of the ports are allocated).
- Added ping resource
