HyperMap is a new format for REST APIs I designed over the past couple of years. It’s built around two core ideas. First, it's entirely self-descriptive, meaning a client can understand and interact with any HyperMap API without custom integration code. Second, it supports running JavaScript or WebAssembly in a secure sandbox on the client side, enabling dynamic functionality that adapts to each API resource’s specific needs.
Think of it as taking the Web stack and stripping out everything designed for humans—the document elements, styling, and visual components—then replacing them with a minimalist, JSON data types (plus a binary type). I kept the familiar Web event model and platform APIs which means that as clients interact with your interface you can trigger dynamic behaviours, exactly as you’d expect from a modern Web app.
A resource then becomes a living thing, dynamically updating based on client interactions or remote events. Clients are now reactive; binding to parts of the data structure and watching for changes. And yes: as people have asked this is still REST — you’re allowed to do this!
- equitiesData:
-
- acornComputersLtd:
-
- ticker:
- ACRN
- price:
- 239.46
- buy:
- sinclairResearchLtd:
-
- ticker:
- SCLR
">Zulip!
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.