RAWS Roadmap

RAWS v4

Version 4 of Rambla Web Services (RAWS) will focus on simplifying the workflow of publishing, distributing, monetizing and managing your content. This should improve fast integration of our services in both front- and back-end applications and enhance usability.

The roadmap for RAWS v4 will be user driven. Please let us know if you have any feature requests: they may become part of this version, or may be implemented in a future version.

Below is the provisional list of RAWS v4 features, classified by service. New features will be added at regular intervals. After a version upgrade has taken place, please look at the release notes for more information.

New features common to all web services

• Creation of workflows
• Support for the JSON format.
• Improve intra-service integration.

META

Features

• Synchronization with various social media

Requested Features

• Resources for channels, playlists
• From/until queries
• Enhanced search possibilities

RATS

Features

• Better integration with META service
• Extended CDN reports

Requested Features

• Improved error handling
• Support for specific source formats

RAMS

Features

• Concurrent users per stream and per minute interval

RAWS v3

All features of RAWS v. 3 have been implemented: the roadmap is completed.

New features common to all web services

• Support for multiple user accounts
• ping resource for for RATS, RASE, RASS and RAMS.
• Improved upload handling
• Invalid filenames (= not according to Rambla conventions) in the SLUG header are renamed automatically by RAWS.

Backward Incompatibilities

• 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.

Feature Requests

• API or new resource to retrieve credit status

RASS

• Support for partial data retrieval (= via the "next" link in the ATOM feed), avoiding too many results in a single response.
• Fileseystem changes are actively synchronized to all CDN nodes => implemented, but currently only on demand
• Support for recursive delete of a directory.
• Automatic creation of sub-dir hierarchies.
• Implementation of the POST method for item and dir resources.
• Support for file and directory tagging: new meta and tag resources.
• Search functionality.

Backward Incompatibilities

• When sending a PUT dir request, the part of the directory hierarchy that doesn't exist will be automatically created. Previously, an error was returned if the parent directory didn't exist.
• Enclosure url inside item (file) entries will refer to the location of the file on the CDN.

RATS

Features

• Additional containers and codecs (e.g. mobile)
• Hot-swappable RATS master

Feature Requests

• Support for 'high priority' transcoding jobs

RAMS

Features

• Support for partial data retrieval (= via the "next" link in the ATOM feed), avoiding too many results in a single response.
• Extended traffic details:
  • Number of RTMP events
  • Percentage downloaded/streamed
  • Time of last download/streaming
• Live-stream traffic details:
  • Number of clients watching for a certain duration
  • Average, total seconds watched
  • Concurrent users per time-unit
• End-user origin:
  • Number of unique users
  • Geographical origin (top 100 by host, city, country)
• Recursive traffic listing (= retrieve traffic for all files under a given root-directory)

Feature Requests

• Search functionality based on tags, (parts of) filenames, amount of traffic...

Backward Incompatibilities

• It is no longer possible to retrieve traffic data for a range of years in a single request. For each year, a seperate request will be needed.

RASE

Features

• 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).
• Retrieval of number of concurrent users (while live-streaming)

META

Features

• Migration of metadata resources to separate service to improve performance, scalability
• Support for JSON requests
• Support for generation of Media RSS playlists
• Automatic creation of META content resource after transcoding

Feature Requests

• Single resource for all files corresponding to a single media item
• Multi-language support