Ethereum jsonrpc

1. Send according to the standard JSON string format

JSON RPC is a standard
wiki.geekdream.com/specification/json RPC_ 2.0. HTML
here is the official document of 2.0. In addition, the package for parsing needs to be introced

2. jsonrpc = new JSONRpcClient("/ json-rpc"); // Instantiate JSON remote call

3. Security is a permanent topic. For web services based on WSDL and soap, we have WS security to guide the implementation of authentication, authorization, identity management and other security requirements. So, is there a mature specification or implementation framework for restful API? How to ensure the security of restful API
how to control the version of restful API
are the verbs given in the HTTP 1.1 specification sufficient for designing restful APIs? Do you expand your verbs in actual projects? When do you need to expand
What are the most valuable features of jax-rs 2.0 released in May this year for the design of rstful API? What problems are they used to solve
can you recommend a practical restful API development framework for InfoQ readers and explain your reasons for promotion
the http2.0 specification is under development. What are your expectations for it
InfoQ: what is a good restful API? I believe everyone has their own criteria. So, what characteristics do you think a good restful API should have?

4. The default value of son-rpc path is: http://localhost : 6800 / jsonrpc after each setting, after entering aria2 again, the json-rpc path will become the default value again. The official website explanation is: the setting of aria2 in yaaw

5. In fact, it's not cheap for C # to call JSON RPC. In general, if C # calls, you can consider using RPC technologies such as WCF
for RPC such as JSON / XML, the following two principles should be followed in C # call:
remote HTTP protocol flow call (use tcpclient / webclient and other class libraries to call content locally)
deserialize the local stream (binary, text JSON / XML, text JSON, etc.) to get the corresponding call
strictly speaking, this situation can not be called RPC. RPC is a remote call, which refers to calling a remote method and returning (not returning) the corresponding response, while JSON / jsonp is to return the execution result in the form of a stream, which can be serialized into a local object. Strictly speaking, JSON / jsonp / XML is actually called by the browser, The browser itself is the host of JavaScript, which can easily reverse the sequence of JSON or directly execute the JSON method
in other words, the browser communication uses the JSON / jsonp scheme, which aims at cross terminal communication. But C # can only appear in the back end of the page. If the back end calls the business layer logic, it is better to use RPC such as WCF directly. Using JSON / jsonp requires custom serialization, which has some problems for future maintenance.

6. 1. Make sure that you can ping. 2. Open the remote connection function of 2003. Right click on the properties of my computer. 3. Set the password for the user name of the remote connection, but no blank password is allowed. 4. Check the firewall. It's better to close the firewall first

7. The content type field in the HTTP header may contain character encoding information. For example, the returned header may contain information like this: content type: text / HTML; charset=UTF-8 This header indicates that the encoding of the page is UTF-8, which is set in the character encoding of the content type in the HTTP header