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 <pieter.wuille@gmail.com>) id 1QrVf3-0005z9-45 for bitcoin-development@lists.sourceforge.net; Thu, 11 Aug 2011 13:51:01 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.47 as permitted sender) client-ip=209.85.216.47; envelope-from=pieter.wuille@gmail.com; helo=mail-qw0-f47.google.com; Received: from mail-qw0-f47.google.com ([209.85.216.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QrVf2-0002tB-DO for bitcoin-development@lists.sourceforge.net; Thu, 11 Aug 2011 13:51:00 +0000 Received: by qwh5 with SMTP id 5so1454503qwh.34 for <bitcoin-development@lists.sourceforge.net>; Thu, 11 Aug 2011 06:50:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.78.197 with SMTP id m5mr6909371qck.268.1313070654941; Thu, 11 Aug 2011 06:50:54 -0700 (PDT) Received: by 10.229.230.72 with HTTP; Thu, 11 Aug 2011 06:50:54 -0700 (PDT) In-Reply-To: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com> References: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com> Date: Thu, 11 Aug 2011 15:50:54 +0200 Message-ID: <CAPg+sBjrq5NG8wavwfpcGLLO2rmY8xLo+BNhDygFU1TS59h-JQ@mail.gmail.com> From: Pieter Wuille <pieter.wuille@gmail.com> To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1QrVf2-0002tB-DO Subject: Re: [Bitcoin-development] Change to multiple executables? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list 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: Thu, 11 Aug 2011 13:51:01 -0000 On Wed, Aug 10, 2011 at 11:36, John Smith <witchspace81@gmail.com> wrote: > All, > > In the current mainline client everything is lugged into one executable > (with an optional daemon-only one). I think this is a bad idea for various > reasons, and would propose something like: > > bitcoind: bitcoin daemon > bitcoin(-qt): bitcoin GUI executable > bitcoincl: bitcoin RPC command line Back on topic: I initially misunderstood your proposal. Let me reformulate, and suggest some names: * bitcoin-gui (or bitcoin-qt): always starts GUI, optionally starts RPC server, no RPC client * bitcoin-server: always starts RPC server, no RPC client, no GUI * bitcoin-client: always runs RPC client, no RPC server, no GUI Additionally, we could offer a script or symlinked executable with names "bitcoin" and "bitcoind" that detect whether RPC commands are present on the command line, and based on this invoke either bitcoin-server/bitcoin-gui or bitcoin-client (for backward compatibility). -- Pieter