Thanks a lot for your explanation.
Anyway, how does JSON-RPC 2.0 over-HTTP work? I think we can implement
MessagePack-RPC like JSON-RPC 2.0.
On Tuesday, October 9, 2012 12:35:53 AM UTC+8, INADA Naoki wrote:
>
> MessagePack-RPC allows asynchronous request.
>
> Client Server
> --- REQ1 -->
>
MessagePack-RPC allows asynchronous request.
Client Server
--- REQ1 -->
--- REQ2 -->
<-- RES2 ---
<-- RES1 ---
But msgpack-rpc's specification doesn't specify how it over HTTP.
(WebSocket, SPDY, HTTP Pipelining or chunked encoding.)
MessagePack-RPC is for stream like pipe, unix domain sock
Sorry for my unfinished sentience.
> At the same time, messages can not be sent from server to client
> proactively.
>
I mean it the HTTP protocol.
> On Monday, October 8, 2012 10:13:56 PM UTC+8, lvqier wrote:
Thank you for your replies.
>
> I have compared the MessagePack-RPC to JSON-RPC 2
Thank you for your replies.
I have compared the MessagePack-RPC to JSON-RPC 2.0 again. The biggest
difference between MessagePack-RPC and JSON-RPC 2.0 is the Notification
message. JSON-RPC 2.0 defines the Notification message as a sub-type of
request message while MessagePack-RPC defines the No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/07/2012 10:38 PM, lvqier wrote:
> I couldn't understand what's the meaning of over-http RPC. As I
> understand, HTTP is a protocol that carries RPC data just like TCP and
> so on. Do you mean RPC protocols that run on HTTP should have
> something
