Sketches of a REST interface to Mailman

.h1 Resource Types

• Lists
• Users
• Subscriptions (which tie together a single user and a single list).
• Messages

.h1 Use Cases

• .h1 Principles

One question is what to use for the representation of each resource? That is, when you access a user's settings by retrieving some URL, what format are the results in? We could use:

• HTML
• An existing XML format for representing data structures, such as XML-RPC's serialization.
• A custom-designed XML format.

• JSON

I suggest using JSON. Libraries are available for most relevant programming languages and it's reasonably human-readable. Designing a custom XML format seems unnecessary, but there's no obvious standard format to use.

.h1 URL Space

• Initial Considerations

• Initial URL design

• Original Use Cases

• restserver-branch

Comments