From: Wendell <w@grabhive•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
Date: Fri, 9 Aug 2013 15:05:04 +0200 [thread overview]
Message-ID: <E211ED41-69BF-4AC9-A6B1-F4E89D16E5C8@grabhive.com> (raw)
In-Reply-To: <CANEZrP1XYyO0aspJ-A-0+_pRDKrtaHZrNTjfOnxBGX8Beiw2Xw@mail.gmail.com>
"Packaged app pages always load locally. This allows apps to be less dependent on the network. Once a user installs an app, they have full control over the app's lifecycle. Apps open and close quickly, and the system can shut apps down at any time to improve performance. Users can fully uninstall apps."
Does this mean that upon install, a nice, icon-emblazoned package will drop into my /Applications folder on a Mac, or in my Windows Start menu, etc... Or are packaged apps always launched and maintained from within Chrome itself?
Provided that the technical stuff could be made to work within the context of the more limited API, this certainly seems like an interesting, user-friendly way to distribute a Bitcoin wallet!
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
On Aug 9, 2013, at 2:14 PM, Mike Hearn wrote:
> Oh, I forgot to make it clear - Chrome apps/extensions can make raw TCP socket connections:
>
> http://blog.chromium.org/2012/11/introducing-tcp-listen-new-api-for.html
>
> You would do it as a packaged app: http://developer.chrome.com/apps/about_apps.html because then they're a lot more similar to native apps (they get their own windows, run offline, etc).
>
> But these aren't standard APIs. They're all Chrome extensions. I doubt HTML5 will support USB access anytime soon, for instance, but packaged apps do.
next prev parent reply other threads:[~2013-08-09 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 11:32 Wendell
2013-08-09 11:48 ` Mike Hearn
2013-08-09 12:05 ` Wendell
2013-08-09 12:10 ` Mike Hearn
2013-08-09 12:14 ` Mike Hearn
2013-08-09 13:05 ` Wendell [this message]
2013-08-13 5:26 ` Chris Double
2013-08-09 13:08 ` Jeff Garzik
2013-08-09 17:58 ` Wendell
2013-08-09 18:09 ` Jeff Garzik
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=E211ED41-69BF-4AC9-A6B1-F4E89D16E5C8@grabhive.com \
--to=w@grabhive$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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