1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
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 <will@phase.net>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <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
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 <bitcoin-development@lists.sourceforge.net>
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: <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: 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 <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"><<a =
href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></=
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'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--
|
