Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UwWCz-0001SU-81 for bitcoin-development@lists.sourceforge.net; Tue, 09 Jul 2013 11:35:49 +0000 X-ACL-Warn: Received: from mail-qc0-f173.google.com ([209.85.216.173]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UwWCx-0007EH-IE for bitcoin-development@lists.sourceforge.net; Tue, 09 Jul 2013 11:35:49 +0000 Received: by mail-qc0-f173.google.com with SMTP id l10so2888703qcy.4 for ; Tue, 09 Jul 2013 04:35:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=ekXqWz0JT2D8FPCjGcvohNcly4g3VQomAsWxjKO6V9E=; b=LmMA7LOUqAlkXbc+4syUX3Av+jOm+z3VD/QE7S6eGkDGw9oEaSiVAR/NTe4aYa1plW q6mNIcitKZMo6kWfHYmUehq9TpCbsgprFyj5FpY1rkHXZMdaYoZ3knFfscaBn2K/O4gw /l3BqMp5KSOfWIPj1AjS+AumgxMSIjBpqOIaGBb1jb9bumu7jofAt6tsDyho+Bkdpl1m LyAnMukx+mEPSnUfm2IkMGNS9LznQUFyT3D0HRrvKkqgy/oN/urfRMGRBvVmGy9DJiG1 eTIZla0aIluH1misv/UCSqkZeXZ/7KQtBcy+9BZHvAMSFQqBEjaOKqgonm2IkTwTwQ9j XsHQ== X-Received: by 10.49.58.70 with SMTP id o6mr19806415qeq.1.1373368416199; Tue, 09 Jul 2013 04:13:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.119.133 with HTTP; Tue, 9 Jul 2013 04:13:16 -0700 (PDT) In-Reply-To: References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com> <1372605569.4937.140661250186789.39404E47@webmail.messagingengine.com> <51DB6548.5070909@lavabit.com> <1373367371.4283.140661253533454.0D7E544E@webmail.messagingengine.com> From: Will Date: Tue, 9 Jul 2013 13:13:16 +0200 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=047d7b2e529097f9dd04e112402d X-Gm-Message-State: ALoCoQkE66EUzPFvyvGNGSYr29OUxj6OimcOTcgCNkgx7Gq1qfI7LGthvZw3xiWiN/aodTdtE6RW X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1UwWCx-0007EH-IE Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 11:35:49 -0000 --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 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
Omaha - which is the automatic update framework that Googl= e Chrome uses - is open sourced:


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 exi= sting auto update framework that we can modify to support threshold signed = updates? I'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.
--047d7b2e529097f9dd04e112402d--