From: Theodore Witkamp <theodore.witkamp@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Release priorities for v0.4?
Date: Wed, 15 Jun 2011 10:32:39 -0700 [thread overview]
Message-ID: <BANLkTinKvkGb4S__9fczOSWadtGZTL87og@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikFaYqvO5=A-eJwR7aBqau+ba5r9Q@mail.gmail.com>
On Wed, Jun 15, 2011 at 9:50 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Wed, Jun 15, 2011 at 10:27 AM, Mark Visser <mjmvisser@gmail.com> wrote:
>> I humbly suggest allowing the wallet.dat location to be specified in the preferences. Being able to easily physically disconnect a wallet by unplugging a USB key seems like a good idea.
>
> That's what -datadir is for. Unfortunately -all- databases must be in
> the datadir, because wallet.dat is a berkeley db, and we need a
> transactional environment. That makes it difficult to move just one
> file.
I am a Berkley DB ignoramus , but how is specifying the wallet file
path different than using a symlink?
Also I think that allowing the user to open more than one wallet helps
the user develop an intuition for the system.
A simple task like opening transferring coins from one to the other is
currently very awkward on the same installation.
Ted
prev parent reply other threads:[~2011-06-15 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 23:59 [Bitcoin-development] Release priorities for v0.4? Jeff Garzik
2011-06-15 14:27 ` Mark Visser
2011-06-15 16:50 ` Jeff Garzik
2011-06-15 17:32 ` Theodore Witkamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinKvkGb4S__9fczOSWadtGZTL87og@mail.gmail.com \
--to=theodore.witkamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox