While working on a demonstrator app for the Reactive + Graph system I’ve been building in my spare time, I found myself wanting to implement a RESTful app protocol on top of WebSockets for in-browser app <-> service communication. I actually searched for “HTTP over WebSockets” but couldn’t find anything promising.
Does anyone know of anything in this space?
The idea is to use one-way messaging as the foundation and build request-response pattern on top. This way I can implement a “subscribe” operation which is necessary for streaming of messages from the service to the browser (and the other way around at some point 🙂
My head got filled up with memories of all the discussions around SOAP/REST and Jim’s and my work on MEST and SSDL (cached version of the original site which is no longer on the web) from more than 10 years ago. Fun times.
Update: I should really be looking at an implementation of HTTP/2 since it has everything I need… single connection, one-way messaging, push from the server, and the familiar verbs/resource-oriented nature of HTTP over the same single connection.
There’s a unique energy that comes with starting something new — a blend of excitement,…
As I continued work on BrainExpanded and its MCP service, I came to realize that…
Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…
After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…
Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…
As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…