MIME-Version: 1.0
In-Reply-To: <CANEZrP3zi4sWBJa-9hu4S2+gT5pP-6JzNi=mJQi=OnzF5iZE_w@mail.gmail.com>
References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
	<CAJHLa0Ncac9Xt-AQBnpghqqpfR-j6Xtd9qVQoUe2dPp0kJvz1A@mail.gmail.com>
	<CANEZrP0k1HDrJC9DOn6JYiVcaRRXwVwxW7ZPjE9XvfTCHXX6pw@mail.gmail.com>
	<CABsx9T3GJN0inGChebJt_dRLpVrPw7BTH8oQo6F4q6yFJaOoCA@mail.gmail.com>
	<CANEZrP3LGxZ6E+9UWQH+_RN66dfeGzo4+QYACjauKRufpqB2QA@mail.gmail.com>
	<1372605569.4937.140661250186789.39404E47@webmail.messagingengine.com>
	<CAKm8k+20z0FkQjnYXjBwUSwY4ncTmMc-LXDH=hF6u55f_gWpkA@mail.gmail.com>
	<CA+i0-i9tj8w7pNuk7nUBQKdxvizX+6_Ez1VA8OtKJNTqRrYtxg@mail.gmail.com>
	<51DB6548.5070909@lavabit.com>
	<CANEZrP0OZZDtRw_KYJpPkhYhQA75h5yyQRQrw+gxV0hsnc2bbg@mail.gmail.com>
	<1373367371.4283.140661253533454.0D7E544E@webmail.messagingengine.com>
	<CANEZrP3zi4sWBJa-9hu4S2+gT5pP-6JzNi=mJQi=OnzF5iZE_w@mail.gmail.com>
From: Will <will@phase.net>
Date: Tue, 9 Jul 2013 13:13:16 +0200
Message-ID: <CAHQs=o5cZCNaiDmH=h3XqxxigWeXbkDMLBr0fSCxTiJtCOJUAA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=047d7b2e529097f9dd04e112402d
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop
 client on bitcoin.org
Precedence: list

--047d7b2e529097f9dd04e112402d
Content-Type: text/plain; charset=ISO-8859-1

Omaha - which is the automatic update framework that Google Chrome uses -
is open sourced:

https://code.google.com/p/omaha/

It might be a bit heavyweight for just one package though.

Will

On 9 July 2013 13:04, Mike Hearn <mike@plan99.net> wrote:

> For the auto update, is there an existing auto update framework that we
> can modify to support threshold signed updates? I'm sure such a thing must
> exist. The updates would download in the background and then the app can
> just ask the user to restart it once the update is locally available, as
> Chrome does.
>

--047d7b2e529097f9dd04e112402d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Omaha - which is the automatic update framework that Googl=
e Chrome uses - is open sourced:<div><br></div><div><a href=3D"https://code=
.google.com/p/omaha/">https://code.google.com/p/omaha/</a></div><div><br></=
div>

<div style>It might be a bit heavyweight for just one package though.</div>=
<div style><br></div><div>Will<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On 9 July 2013 13:04, Mike Hearn <span dir=3D"ltr">&lt;<a =
href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</=
span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div>For the auto update, is there an exi=
sting auto update framework that we can modify to support threshold signed =
updates? I&#39;m sure such a thing must exist. The updates would download i=
n the background and then the app can just ask the user to restart it once =
the update is locally available, as Chrome does.</div>

</div></blockquote></div></div></div></div>

--047d7b2e529097f9dd04e112402d--