Rambla Stream Enabler

From Rambla Wiki

Jump to: navigation, search

Overview

RASE overview

Rambla Stream Enabler (RASE) is both a web service and a web application, designed to automate the set up of live streams. It has a resource oriented architecture that can be accessed by either a web-browser or a REST API.

When setting up a live stream, the RASE client will receive the IP address or domain name of the Wowza Media Server to which an encoder will be able to broadcast. The set up process also includes the possibility for the client to choose a customized Wowza application. The live stream is delivered to end-users through multiple Wowza edge servers on Rambla's high-speed and reliable Content Delivery Network.

Currently, RASE supports broadcasting using an RTSP/RTP or MPEG-TS based encoder and streaming using the Real Time Messaging Protocol (RTMP - Adobe Flash Player) or MPEG2 Transport Streams (MPEG-TS) (set-top boxes and IPTV solutions). With the release of Wowza Media Server 2, future versions of RASE are likely to also support other streaming protocols, like the Real Time Streaming Protocol (QuickTime player and VLC media player and many mobile devices), Microsoft Smooth Streaming (Microsoft Silverlight® player) and Apple HTTP Live Streaming (iPhone™, iPod® touch, Safari® browser, QuickTime® player).

Usage

Requests are sent using the HTTP protocol and require HTTP Basic Authentication. The URI path determines the resource that the request wants to access, and the HTTP method determines the type of action to be taken on this resource. For the available resources and methods, see the RASE API.

When data needs to be transferred in the request body, it must be encoded in one of the formats supported by RASE.

  • HTML forms are supported for web-browser based access.
  • When using RASE as a web-service, the data should be XML formatted: using either a simple XML structure for transferring content-only data, or the more advanced Atom Publishing Protocol (APP) for transferring content and metadata.

The result of a request is conveyed through standard HTTP header mechanisms and, additionally, via custom RAWS status codes and messages. As a rule, the response body (if present) will be encoded in the same format as the request, but the user can override this via the query-string part of the URI.

By conforming to open protocols, Rambla Web Services accommodate for rapid client application development in any programming language. For more information, see the RAWS Clients section.

Getting Started

To get started using RASE, you could watch the introductory screencast or look at this example, showing the communication between RASE and an automated client.

The RAWS Documentation section also contains a getting started page for Rambla Web Services in general.

Personal tools