1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1S3Xa3-00086a-6o
for bitcoin-development@lists.sourceforge.net;
Fri, 02 Mar 2012 18:51:51 +0000
X-ACL-Warn:
Received: from nm18-vm2.bullet.mail.ne1.yahoo.com ([98.138.91.94])
by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1S3XZz-0008CC-CZ for bitcoin-development@lists.sourceforge.net;
Fri, 02 Mar 2012 18:51:51 +0000
Received: from [98.138.90.55] by nm18.bullet.mail.ne1.yahoo.com with NNFMP;
02 Mar 2012 18:51:41 -0000
Received: from [98.138.89.167] by tm8.bullet.mail.ne1.yahoo.com with NNFMP;
02 Mar 2012 18:51:41 -0000
Received: from [127.0.0.1] by omp1023.mail.ne1.yahoo.com with NNFMP;
02 Mar 2012 18:51:41 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 701868.51374.bm@omp1023.mail.ne1.yahoo.com
Received: (qmail 17662 invoked by uid 60001); 2 Mar 2012 18:51:41 -0000
X-YMail-OSG: PUbXg1QVM1mYeCG345DJpaCpciRBAbdB15oAAkvli7goxXX
iYBWPhFn9pxdxoSnN0b0i406AKYOJzRGvXZY.JX53Kw.PsusXKdmYCSiDclK
5wCjRtnJ9h7ns92B4polMpqCwWvHZqDR5QILX3hA9kW.q4Wa4nlznUzX1aHN
Ys51HOVJkz7jgDZxNI7oBDkb.XnVL9kJjj90bgqem.v4VlNdIY0yKhBneO_j
4IfS2pZZtueduTLDU2dOCORaGNz55_IIrr8eppgjQQbb5nDiFS.Aj2fNNF4I
6TGr5FPQJrSGx5CxZNk0jRhY9HPJoZMXxkXi7Q1t5s3kCawTUoXvvZr2OYf8
FNbKNO7xgy6nr9N1aBofAB.iL6NsGgb2ZMZV_EM0.Zc0DYFWd3JXlCpyDidA
qC3aGz8W0IsgS926y7PV_LLZok6uPuuNlMcu1ipiNUTo77EZ2LyEmIQuIunn
7s6Cl0UolR8gNMM4RA9pWBOTXBclom4WK
Received: from [2.97.161.54] by web121006.mail.ne1.yahoo.com via HTTP;
Fri, 02 Mar 2012 10:51:41 PST
X-Mailer: YahooMailWebService/0.8.116.338427
Message-ID: <1330714301.3840.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Fri, 2 Mar 2012 10:51:41 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="285087016-776446052-1330714301=:3840"
X-Spam-Score: 0.9 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.94 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1S3XZz-0008CC-CZ
Subject: [Bitcoin-development] JSON-RPC is BIP territory or not?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:51:51 -0000
--285087016-776446052-1330714301=:3840
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,=0A=0AI got sent this BIP:=0A=0Ahttps://en.bitcoin.it/wiki/BIP_DRAFT:_ge=
tmemorypool#JSON-RPC_Method:_getmemorypool=0A=0A=0AWhat is your opinion on =
this? Is it BIP related?=0A=0AIt is a implementation-specific non-bitcoin-p=
rotocol proposal. My understanding of BIPs is that=0Athey apply across bitc=
oin implementations and largely focus on the most generic use-cases=0A(like=
the URIs) and the protocol. Things which affect all clients, and allow the=
system to function=0Aas a united whole.=0A=0AThat BIPs especially focus on=
the protocol, and that something like this is outside the mandate=0Aof the=
BIP process.=0A=0AFor instance, we could imagine a future scenario. Bitcoi=
n-Qt is currently based off bitcoind's=0Acodebase. However wumpus built the=
client in mind with an abstraction layer to enable multiple=0Abackends (a =
good design). In our hypothetical situation, there are 3 different backend =
codebases=0Ausing=A0Bitcoin-Qt. I do not think a proposal to mandate a chan=
ging to Bitcoin-Qt's abstraction=0Alayer or a change in the UI placement wo=
uld be appropriate BIP material.=0A=0AOTOH, many clients do need to make us=
e of URIs and the BIP process is totally correct, as it=0Astandardises a be=
haviour which is needed for interoperability of the network and community.=
=0A=0AThoughts?
--285087016-776446052-1330714301=:3840
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div>Hi,</div><div><b=
r></div><div>I got sent this BIP:</div><div><br></div><div><a href=3D"https=
://en.bitcoin.it/wiki/BIP_DRAFT:_getmemorypool#JSON-RPC_Method:_getmemorypo=
ol">https://en.bitcoin.it/wiki/BIP_DRAFT:_getmemorypool#JSON-RPC_Method:_ge=
tmemorypool</a><br></div><div><br></div><div>What is your opinion on this? =
Is it BIP related?</div><div><br></div><div>It is a implementation-specific=
non-bitcoin-protocol proposal. My understanding of BIPs is that</div><div>=
they apply across bitcoin implementations and largely focus on the most gen=
eric use-cases</div><div>(like the URIs) and the protocol. Things which aff=
ect all clients, and allow the system to function</div><div>as a united who=
le.</div><div><br></div><div>That BIPs especially focus on the protocol, an=
d that something like this is outside the mandate</div><div>of the BIP
process.</div><div><br></div><div>For instance, we could imagine a future =
scenario. Bitcoin-Qt is currently based off bitcoind's</div><div>codebase. =
However wumpus built the client in mind with an abstraction layer to enable=
multiple</div><div>backends (a good design). In our hypothetical situation=
, there are 3 different backend codebases</div><div>using <span style=
=3D"font-size: 12pt; ">Bitcoin-Qt. I do not think a proposal to mandate a c=
hanging to Bitcoin-Qt's abstraction</span></div><div>layer or a change in t=
he UI placement would be appropriate BIP material.</div><div><br></div><div=
>OTOH, many clients do need to make use of URIs and the BIP process is tota=
lly correct, as it</div><div>standardises a behaviour which is needed for i=
nteroperability of the network and community.</div><div><br></div><div>Thou=
ghts?</div></div></body></html>
--285087016-776446052-1330714301=:3840--
|
