Clean up HTTP and JSON-RPC parsing code #7
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
Depends on
#3 Support bi-directional JSON-RPC 2.0
p/json-rpc-shell
#5 json-rpc-test-server: add a pure HTTP listener
p/json-rpc-shell
Reference: p/json-rpc-shell#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.