You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rustatian opened this issue
Sep 29, 2023
· 0 comments
Assignees
Labels
C-feature-acceptedCategory: Feature discussed and acceptedhelp-needed-hardCall for participation: Experience needed to fix: Hard / a lotS-RFCRequest: Request for comments
In the RoadRunner we have a lot of the different RPC methods that are used to send the data to the JOBS drivers, control/monitor different plugins, reset RR, show info about the workers, etc. Since RPC is a good way to send some data, it is hard to do that outside the RR environment.
This proposal is about adding an HTTP/1.1 server to the RPC plugin to allow users to send HTTP requests, which would be automatically converted to the internal RPC format.
For example, to send a JOB to the JOBS plugin user would have two options:
Use our regular RPC methods to do that.
Use HTTP POST request.
Docs:
Should be added complete documentation (swagger) about plugins HTTP handlers.
The text was updated successfully, but these errors were encountered:
C-feature-acceptedCategory: Feature discussed and acceptedhelp-needed-hardCall for participation: Experience needed to fix: Hard / a lotS-RFCRequest: Request for comments
Plugin
RPC
I have an idea!
In the RoadRunner we have a lot of the different RPC methods that are used to send the data to the JOBS drivers, control/monitor different plugins, reset RR, show info about the workers, etc. Since RPC is a good way to send some data, it is hard to do that outside the RR environment.
This proposal is about adding an HTTP/1.1 server to the RPC plugin to allow users to send HTTP requests, which would be automatically converted to the internal RPC format.
For example, to send a JOB to the JOBS plugin user would have two options:
Docs:
The text was updated successfully, but these errors were encountered: