📅 Original date posted:2012-03-03
📝 Original message:On Saturday, March 03, 2012 10:05:58 AM Gavin Andresen wrote:
> > HTTP and JSON-RPC are a client-server model; there is no way for the
> > server to make calls to the client. It's not practical to expect clients
> > to run their own JSON-RPC server - many cannot listen on WAN ports at
> > all.
>
> You're doing that thing where either you say something before you've
> done adequate research, or you're being needlessly pedantic; I just
> copied and pasted this from section 2.1 of the JSON-RPC spec:
I wasn't aware anyone was considering JSON-RPC over anything other than HTTP.
I've updated the draft to include long polling, and remove some assumptions of
using HTTP for transport.
Luke-Jr [ARCHIVE] /
npub1dt…u7wrs
2023-06-07 03:11:59
in reply to nevent1q…q0h4
Author Public Key
npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrsPublished at
2023-06-07 03:11:59Event JSON
{
"id": "5bd135302d17c5df6bf523763cd5b2963fe3d70ab9f42eb6a794e4c5d5d93134",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686107519,
"kind": 1,
"tags": [
[
"e",
"3c851c8f17df1dd68608e4374d6cde0ed02a6a2268be0433e6610590ab1017ab",
"",
"root"
],
[
"e",
"acc5155efa93da319706e5fa18bde5a15153ef6c0541d9d07d62856e2d23fa59",
"",
"reply"
],
[
"p",
"49f07bd32c0108a2903a0fa59f904ed312e0ea427d3269eb5fa910eb4a9e22c4"
]
],
"content": "📅 Original date posted:2012-03-03\n📝 Original message:On Saturday, March 03, 2012 10:05:58 AM Gavin Andresen wrote:\n\u003e \u003e HTTP and JSON-RPC are a client-server model; there is no way for the\n\u003e \u003e server to make calls to the client. It's not practical to expect clients\n\u003e \u003e to run their own JSON-RPC server - many cannot listen on WAN ports at\n\u003e \u003e all.\n\u003e \n\u003e You're doing that thing where either you say something before you've\n\u003e done adequate research, or you're being needlessly pedantic; I just\n\u003e copied and pasted this from section 2.1 of the JSON-RPC spec:\n\nI wasn't aware anyone was considering JSON-RPC over anything other than HTTP.\n\nI've updated the draft to include long polling, and remove some assumptions of \nusing HTTP for transport.",
"sig": "de61056d1b9fcae5c1c78632675e5a246184e0b9c9b749bf806fc1653920b68e7c0fd8d66309de989230caf61259bdd23cfffcd9c694612912111fc1faf2de28"
}