📅 Original date posted:2012-03-03
📝 Original message:> I've updated the draft to include long polling, and remove some assumptions of
> using HTTP for transport.
Looks good to me.
On 3/3/2012 4:44 PM, Luke-Jr wrote:
> 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.
>
> ------------------------------------------------------------------------------
> Virtualization& Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Stefan Thomas [ARCHIVE] /
npub1f8…ap20e
2023-06-07 03:12:02
in reply to nevent1q…cevl
Author Public Key
npub1f8c8h5evqyy29yp6p7jelyzw6vfwp6jz05exn66l4ygwkj57ytzqmap20eSeen on
wss://relay.nostr.bandPublished at
2023-06-07 03:12:02Event JSON
{
"id": "1d07aef20ebb8e2ef7a2d4d379b8abee9c1d671be02d1a6029aa3abfd8c29c2e",
"pubkey": "49f07bd32c0108a2903a0fa59f904ed312e0ea427d3269eb5fa910eb4a9e22c4",
"created_at": 1686107522,
"kind": 1,
"tags": [
[
"e",
"3c851c8f17df1dd68608e4374d6cde0ed02a6a2268be0433e6610590ab1017ab",
"",
"root"
],
[
"e",
"5bd135302d17c5df6bf523763cd5b2963fe3d70ab9f42eb6a794e4c5d5d93134",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2012-03-03\n📝 Original message:\u003e I've updated the draft to include long polling, and remove some assumptions of\n\u003e using HTTP for transport.\n\nLooks good to me.\n\nOn 3/3/2012 4:44 PM, Luke-Jr wrote:\n\u003e On Saturday, March 03, 2012 10:05:58 AM Gavin Andresen wrote:\n\u003e\u003e\u003e HTTP and JSON-RPC are a client-server model; there is no way for the\n\u003e\u003e\u003e server to make calls to the client. It's not practical to expect clients\n\u003e\u003e\u003e to run their own JSON-RPC server - many cannot listen on WAN ports at\n\u003e\u003e\u003e all.\n\u003e\u003e You're doing that thing where either you say something before you've\n\u003e\u003e done adequate research, or you're being needlessly pedantic; I just\n\u003e\u003e copied and pasted this from section 2.1 of the JSON-RPC spec:\n\u003e I wasn't aware anyone was considering JSON-RPC over anything other than HTTP.\n\u003e\n\u003e I've updated the draft to include long polling, and remove some assumptions of\n\u003e using HTTP for transport.\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Virtualization\u0026 Cloud Management Using Capacity Planning\n\u003e Cloud computing makes use of virtualization - but cloud computing\n\u003e also focuses on allowing computing to be delivered as a service.\n\u003e http://www.accelacomm.com/jaw/sfnl/114/51521223/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e",
"sig": "c75d626e1462258fafee568dccef6c3508ad257bb4b8702f5dd7ecaadd2e5abaed3c6cf630f9916795d227a8a3ff5842dc3883fe30a08042d4a551f1a541da43"
}