Repository navigation
oRPC over CoAP instead of HTTP(S) #2171
Description
Describe the feature
So i was thinking about supporting non HTTP protocols or similar ones such as CoAP for microcontrollers and IoT devices (CoAP can run on DTLS/TLS/Websockets etc maybe thats a factor aswell? would like to try DTLS approach for microcontroller usage)
How hard would it be to adapt oRPC to work on other custom protocols that are not HTTP? is there a built in easy way to do this?
Sorry if this is a stupid question with an easy answer.
If it isn't that hard to do i might be willing to help implement it
On a side note is there any universal base oRPC runs ontop of that then can be adapted for all protocols etc? like a master class that applies to all protocols then specific implementations very by implementation so it can be adapted for and maybe have plugins for each protocol it supports?
Additional information
- Would you be willing to help implement this feature?
Activity
pullfrog commentedon Oct 2, 2026
dinwwwh commentedon Oct 2, 2026
oRPC is based on https://github.com/middleapi/standard-server - all you need is create another standard-server adapters, and seem this is long running connection, you can check existing peer adapter (things powered oRPC websocket, message port adapters)