Clean up HTTP and JSON-RPC parsing code #7

Open
opened 3 years ago by p · 0 comments
p commented 3 years ago
Owner

http_parserpp may be employed in json-rpc-test-server. backend_co_on_data etc. can then be deduplicated.

In the bi-directional mode the shell may act as a server and JSON-RPC parsing code can similarly be shared between the two programs. We need to be able to distinguish request from responses and branch accordingly. Think about detecting probable JSON-RPC 1.0 requests and responses--maybe just look at object field names.

`http_parserpp` may be employed in json-rpc-test-server. `backend_co_on_data` etc. can then be deduplicated. In the bi-directional mode the shell may act as a server and JSON-RPC parsing code can similarly be shared between the two programs. We need to be able to distinguish request from responses and branch accordingly. Think about detecting probable JSON-RPC 1.0 requests and responses--maybe just look at object field names.
p added this to the v1.2.0 milestone 3 years ago
p self-assigned this 3 years ago
p added a new dependency 3 years ago
p added a new dependency 3 years ago
p added this to the v1.2.0 project 3 years ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: p/json-rpc-shell#7
Loading…
There is no content yet.