Implement Bi-directional Communication

[JayChoi1736]

Proposed changes

• This PR is derived from go-ethereum PRs

  • rpc: implement full bi-directional communication ethereum/go-ethereum#18471
  • rpc: implement websockets with github.com/gorilla/websocket  ethereum/go-ethereum#19866
  • p2p/simulations: use github.com/gorilla/websocket ethereum/go-ethereum#20289

• Fixed

  • rpc: fix client shutdown hang when Close races with Unsubscribe ethereum/go-ethereum#17894
  • Can not use klaytn client to dial with websocket #1111
  • rpc: cancel root context after all requests are served ethereum/go-ethereum#19430
  • rpc: fix rare deadlock when canceling HTTP call context ethereum/go-ethereum#19715

• Changed

  • rewrite of the server-side code. JSON-RPC processing code is now the same on both server and client side.
  • New APIs added:

    client.Notify(ctx, method, args...)     // sends a notification
    ClientFromContext(ctx)                  // to get a client in handler method
    

  • makes package rpc to use the github.com/gorilla/websocket package for WebSockets.
  • DialWebsocket's handling of the default Origin header has changed( from localhost's hostname -> creating connections without an Origin header) The origin check is supposed to protect against browser based attacks. Browsers always set Origin. Non-browser software can put anything in origin and checking it doesn't provide additional security.
  • rpc pending request limit checking logic changed slightly.
  • CodecOption is deprecated

• Test

  • test klaytn-rpc-tester on http, fasthttp - rpc, websocket
  • checked api-server performance
  • add a few unit test cases
  • check rpc-related counters (rpcTotalRequestsCounter, rpcPendingRequestCount, rpcSuccessResponsesCounter, rpcErrorResponsesCounter, rpcPendingRequestCount, wsSubscriptionReqCounter, wsUnsubscriptionReqCounter, wsConnCounter)

Types of changes

Please put an x in the boxes related to your change.

• Bugfix
• New feature or enhancement
• Others

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING GUIDELINES doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes ($ make test)
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Related issues

• solve Can not use klaytn client to dial with websocket #1111
• supersede rpc: implement gorilla websocket #1170

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[JayChoi1736]

for reviewers:

• the main difference between this PR and ethereum PRs( #18471, #19866 , #20289 ) is about metrics and limit.
  • metrics : rpcTotalRequestsCounter, rpcPendingRequestsCount, rpcSuccessResponsesCounter, rpcErrorResponsesCounter, rpcPendingRequestsCount, wsSubscriptionReqCounter, wsUnsubscriptionReqCounter, wsConnCounter
  • limit : MaxrequestContentLength, pendingRequestLimit, MaxSubscriptionPerWSConn, WebsocketReadDeadLine, WebsocketWriteDeadline, MaxWebsocketConnections, NonEthCompatible
  • handling logic of rpcPendingRequestCount and pendingRequestLimit is slicely changed. Formal logic counts pendingRequest only on multi-shot connections, but new logic will counts single-shot connections' requests as pendingRequest.
• some rpc log msgs are added

[jiseongnoh]

Looks good!

[hyunsooda]

Checked only the changes of SC package-related ones and confirmed no backward compatibility issue was discovered.
Cross-check please, @henry-will

[henry-will]

I have reviewed about node/sc in this time.