Michael Grønager [ARCHIVE] on Nostr: 📅 Original date posted:2012-03-03 📝 Original message:> > HTTP and JSON-RPC are ...
đź“… Original date posted:2012-03-03
📝 Original message:>
> 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.
Well, I think what Stefan had in mind was http keep-alive combined with an event system. So similar to the way a web chat application work, just for json-rpc. BitcoinJS already uses this for realtime updating a webwallet. Libcoin is also prepared for this with a quite advanced, non-blocking, http server so I second Stefan that an update function could indeed be of relevance.
Btw - question to Stefan as the JavaScript guru - what do you consider the standard/defacto-standard/right/best-practice way of doing S->C json-rpc, what (javascript) library do you use for this?
Cheers,
Michael
>
> ------------------------------------------------------------------------------
> 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-developmentPublished at
2023-06-07 03:11:53Event JSON
{
"id": "5c7fcd69965962abe330aeb0ceed5acca80b86564309036726e56d3624bdafc8",
"pubkey": "a277336e95d2d0a831fff67fc80d8082322689a88ede9f877fa246a02629a43f",
"created_at": 1686107513,
"kind": 1,
"tags": [
[
"e",
"3c851c8f17df1dd68608e4374d6cde0ed02a6a2268be0433e6610590ab1017ab",
"",
"root"
],
[
"e",
"7cc52547a541a93d2619e570552207d2db1709448425594e8b69809d23d749ec",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2012-03-03\n📝 Original message:\u003e \n\u003e HTTP and JSON-RPC are a client-server model; there is no way for the server to \n\u003e make calls to the client. It's not practical to expect clients to run their \n\u003e own JSON-RPC server - many cannot listen on WAN ports at all.\n\nWell, I think what Stefan had in mind was http keep-alive combined with an event system. So similar to the way a web chat application work, just for json-rpc. BitcoinJS already uses this for realtime updating a webwallet. Libcoin is also prepared for this with a quite advanced, non-blocking, http server so I second Stefan that an update function could indeed be of relevance.\n\nBtw - question to Stefan as the JavaScript guru - what do you consider the standard/defacto-standard/right/best-practice way of doing S-\u003eC json-rpc, what (javascript) library do you use for this?\n\nCheers,\n\nMichael\n\n\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",
"sig": "800e76b03ed4b0d7aef0f52367432456b714d9369cb84ed257c84deee782b1502f02eb9ccc4609c46ec90b01a0a27b533768b99a589df26e7bb9ded5089d6f80"
}