webmachine
cl-webgl-demo
webmachine | cl-webgl-demo | |
---|---|---|
2 | 1 | |
1,498 | 1 | |
-0.1% | - | |
2.9 | 2.4 | |
3 months ago | 12 months ago | |
Erlang | Common Lisp | |
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webmachine
- Work in progress on a port of Webmachine
-
Best Practices for REST API Design
I interrupted my reading at 'Accept and respond with JSON' to write this comment, before I skipped over that section and returned to reading the rest.
Folks that aren't aware of Webmachine should take a look:
https://github.com/webmachine/webmachine
The 'Accept' header should determine the response type, but content negotiation is something that few bother to implement. Webmachine does that for you.
Also, shameless plug for my OCaml port:
https://github.com/inhabitedtype/ocaml-webmachine
cl-webgl-demo
-
Work in progress on a port of Webmachine
Here is the code with my modifications to make it work with current JS libs: https://github.com/svetlyak40wt/cl-webgl-demo
What are some alternatives?
api-guidelines - Microsoft REST API Guidelines
cl-webmachine - HTTP Semantic Awareness on top of Hunchentoot
OpenAPI-Specification - The OpenAPI Specification Repository
snooze - Common Lisp RESTful web development
google.aip.dev - API Improvement Proposals. https://aip.dev/
swagger-tools - A Node.js and browser module that provides tooling around Swagger.
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
http-decision-diagram - An activity diagram to describe the resolution of HTTP response status codes, given various headers.