RestMS provides web applications with enterprise-level messaging via an asynchronous RESTful interface that works over standard HTTP/HTTPS.
This is the home of the RestMS community, for those helping to develop the RestMS specification, those making implementations, and users who want to help steer the process.
New here? Don't know what this site is all about? ยป Get started, then:
- Register to become a contributor
- Discuss anything you read on this site
- Create your own specifications
- Fork a specification
- Implement a specification in your own code
Specifications
| Raw | Draft | Stable | Legacy | Retired | Deleted |
4/AMQP9 - an AMQP/0.9.1 profile for RestMS - Raw
This document defines the AMQP9 profile for RestMS. The AMQP9 profile defines the behaviour of a set of feed, join, and pipe types that provide an AMQP/0.9.1-interoperable messaging model. (12 Apr 2009 11:40)
3/Defaults - a default profile for RestMS - Raw
This document defines the Defaults profile for RestMS. The Defaults profile defines the behavior of the default feed, join and pipe types. This profile provides the basis for simple pub-sub (the "Parrot" pattern) and request-response (the "Housecat" pattern) applications. (12 Apr 2009 11:40)
2/RestMS - a RESTful Messaging Service - Draft
This document defines RestMS, a RESTful Messaging Service. RestMS provides web applications with enterprise-level messaging via an asynchronous RESTful interface that works over plain HTTP/HTTPS. RestMS extends RestTL and is itself extended through optional profiles. (12 Apr 2009 11:37)
1/RestTL - a RESTful Transport Layer - Draft
This document defines a RESTful Transport Layer (RestTL), a way of working with server-held resources in a RESTful fashion. RestTL specifies standard rules for representing resources, and standard mechanisms for working with them in a RESTful fashion over a plain HTTP client-server network. (12 Apr 2009 11:28)
Open issues
ยป How to submit an issue | All issues
All contributors to the site need to accept a contributor policy, which protects RestMS from confusion over patents or copyright. If you're not already registered, please register so you can create your issue. Thanks!
The RestMS Stack
| Layer | What exists |
|---|---|
| Application | Client bindings |
| Profile | 3/Defaults 4/AMQP9 โฆ |
| Semantic | 2/RestMS |
| Transport | 1/RestTL |
| Wire-level | HTTP/HTTPS |
RestMS Implementations
- Ahkera by Thilo Fromm, in Python/Django.
- Zyre by iMatix, in C (part of OpenAMQ package).
- Client stack in Perl by iMatix (in RestMS git)
Articles on RestMS
- RestMS Presentation at FrOSCon 2009 - Pieter Hintjens and Thilo Fromm introduced the RestMS protocol and RestMS.org's standardisation process at FrOSCon 2009 (www.froscon.org/).
- Introduction to RestMS - In this article Pieter Hintjens introduces RestMS, the RESTful Messaging Service. RestMS is a new standard for real web messaging that offers simple, scalable, and secure data delivery over ordinary HTTP.
- Twitter for Applications - RestMS might be described as "Twitter for applications" because it makes it easy for applications to join together. This article explains RestMS by comparing it to alternatives, and provides some typical use cases.
Recent comments
Chatter
- Lightning talk at Euro DjangoCon - There was a RestMS lightning talk at Euro Djangocon. Slides are available here: https://www.thilo-fromm.de/~t-lo/slides/RestMS_light/rmslt.pdf
- RestMS presentation - An introduction to RestMS, as an online presentation, and downloadable as a PDF.
- Thilo Fromm starts a new RestMS server - Thilo Fromm announced a new RestMS project based on Python and Django, on 10 April 2009:
- Steve Vinoski: REST, Reuse and Serendipity - A slide show from Steve Vinoski called "REST, Reuse and Serendipity" explains (though this was not Steve's goal in the slide show) why we need RestMS.
Recently
spec:2/RestMS - a RESTful Messaging Service
main:Start
wiki:Housecat
wiki:Reverse Housecat
main:Discussion
main:Getting Started
wiki:Wolf Call
wiki:Wolfpack