Tomeu Vizoso wrote:
>> Another issue is how we integrate the updater with addons.sl.o.
>> Because the OLPC microformat is trivial, it might be easy to modify
>> the remora's html output to be compatible with it. Mick, Tomeu and
>> David, who have had a closer look at the code, might want to commen
On Mon, Feb 2, 2009 at 10:46, Bernie Innocenti wrote:
> C. Scott Ananian wrote:
>> OK, thanks. The existing updater works fine in Debian; I don't know
>> if it was ever pushed into koji, but it is certainly compatible with
>> Fedora. If anyone wants to develop a new updater, I can probably
>> of
On Wed, Feb 4, 2009 at 8:20 AM, Benjamin M. Schwartz
wrote:
> I am finally understanding Martin's dilemma.
>
> Every version of every Activity can potentially specify a different update
Bingo. Teh interwebs has these things called redirects, and they're
used all the bloody time, because stuff mov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Langhoff wrote:
> On Wed, Feb 4, 2009 at 7:21 AM, C. Scott Ananian wrote:
>> On Mon, Feb 2, 2009 at 11:19 PM, Martin Langhoff
>>> All I can suggest is that you go back on this thread and read my email.
>>>
>>> Here's a clarification (I know my
On Sun, 1 Feb 2009, Marco Pesenti Gritti wrote:
> On Fri, Jan 30, 2009 at 9:54 PM, Michael Stone wrote:
>> Dear Sugar team,
>>
>> I've been very confused (and frankly, significantly angered) by recent
>> remarks that I've encountered both in person (e.g. from Bernie) and in
>> #sugar (e.g. fro
On Wed, Feb 4, 2009 at 7:21 AM, C. Scott Ananian wrote:
> On Mon, Feb 2, 2009 at 11:19 PM, Martin Langhoff
>> All I can suggest is that you go back on this thread and read my email.
>>
>> Here's a clarification (I know my writing isn't always clear): the url
>> in the metadata is not expected to r
On Mon, Feb 2, 2009 at 11:19 PM, Martin Langhoff
wrote:
> On Tue, Feb 3, 2009 at 5:10 PM, C. Scott Ananian wrote:
>> You failed to convince me. How (...)?
>
> All I can suggest is that you go back on this thread and read my email.
>
> Here's a clarification (I know my writing isn't always clear)
On Tue, Feb 3, 2009 at 5:10 PM, C. Scott Ananian wrote:
> You failed to convince me. How (...)?
All I can suggest is that you go back on this thread and read my email.
Here's a clarification (I know my writing isn't always clear): the url
in the metadata is not expected to remain static over ti
On Mon, Feb 2, 2009 at 10:53 PM, Martin Langhoff
wrote:
> On Tue, Feb 3, 2009 at 3:46 PM, C. Scott Ananian wrote:
>> "Only works with HTTP" -- that's why were are careful to make our
>> protocols only use HTTP.
>
> Several of our protocols are http based, but not all.
Please be specific.
> What
On Tue, Feb 3, 2009 at 3:46 PM, C. Scott Ananian wrote:
> "Only works with HTTP" -- that's why were are careful to make our
> protocols only use HTTP.
Several of our protocols are http based, but not all.
What I am stating is that for almost all protocols we need a service
announcement scheme to
On Mon, Feb 2, 2009 at 4:34 PM, Martin Langhoff
wrote:
> On Tue, Feb 3, 2009 at 1:20 AM, C. Scott Ananian wrote:
>> I don't understand your problem.
>
> How does the XS know what URLs to mask?
>
> For example, say the current version of Foo.xo (which the XS has) has
> a url of http://sugarlabs.or
On Tue, Feb 3, 2009 at 3:28 PM, Benjamin M. Schwartz
wrote:
>> How does the XS know what URLs to mask?
>
> Surely the URLs to mask are the source URLs of the .xo bundles in
Hi Ben,
The gotcha is described in the paragraph you snipped :-) right after
my question.
I try hard to avoid asking very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Langhoff wrote:
> On Tue, Feb 3, 2009 at 1:20 AM, C. Scott Ananian wrote:
>> I don't understand your problem.
>
> How does the XS know what URLs to mask?
Surely the URLs to mask are the source URLs of the .xo bundles in
question, right? So i
On 2 Feb 2009, at 22:30, Martin Langhoff wrote:
> On Tue, Feb 3, 2009 at 10:50 AM, Gary C Martin
> wrote:
>> pull it back on list), but while trying to follow this thread I'd
>> been
>> assuming one of the XS functions is as an http proxy cache server
>> (squid or
>> some such). This wouth
On Tue, Feb 3, 2009 at 10:50 AM, Gary C Martin wrote:
> pull it back on list), but while trying to follow this thread I'd been
> assuming one of the XS functions is as an http proxy cache server (squid or
> some such). This wouth then help reduce common internet traffic via caching;
> one person d
On Mon, Feb 2, 2009 at 4:34 PM, Martin Langhoff
wrote:
> On Tue, Feb 3, 2009 at 1:20 AM, C. Scott Ananian wrote:
>> I don't understand your problem.
>
> How does the XS know what URLs to mask?
How does my proxy cache know what URLs to cache?
> All this specialcasing and cheat-sheet exceptions o
On Tue, Feb 3, 2009 at 1:20 AM, C. Scott Ananian wrote:
> I don't understand your problem.
How does the XS know what URLs to mask?
For example, say the current version of Foo.xo (which the XS has) has
a url of http://sugarlabs.org/activities/ in its metadata but _old_
versions of the same activi
On Mon, Feb 2, 2009 at 8:56 AM, Ties Stuij wrote:
> On Mon, Feb 2, 2009 at 11:23 AM, C. Scott Ananian wrote:
>> On Sun, Feb 1, 2009 at 9:24 PM, Martin Langhoff
>> wrote:
>>> So this depends on a simple service-announcement scheme. I'll sidestep
>>> the how of it, and say:
>>>
>>> When Sugar know
On Mon, Feb 2, 2009 at 11:23 AM, C. Scott Ananian wrote:
> On Sun, Feb 1, 2009 at 9:24 PM, Martin Langhoff
> wrote:
>> So this depends on a simple service-announcement scheme. I'll sidestep
>> the how of it, and say:
>>
>> When Sugar knows that there is a local "activity install/update"
>> server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 02, 2009 at 07:25:54AM -0500, C. Scott Ananian wrote:
>On Mon, Feb 2, 2009 at 6:46 AM, Jonas Smedegaard wrote:
>> On Mon, Feb 02, 2009 at 10:46:35AM +0100, Bernie Innocenti wrote:
>>>C. Scott Ananian wrote:
OK, thanks. The existing
Bernie Innocenti wrote:
> Another issue is how we integrate the updater with addons.sl.o.
> Because the OLPC microformat is trivial, it might be easy to modify
> the remora's html output to be compatible with it. Mick, Tomeu and
> David, who have had a closer look at the code, might want to commen
On Mon, Feb 2, 2009 at 6:46 AM, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Feb 02, 2009 at 10:46:35AM +0100, Bernie Innocenti wrote:
>>C. Scott Ananian wrote:
>>> OK, thanks. The existing updater works fine in Debian; I don't know
>>> if it was ever push
On Mon, Feb 2, 2009 at 4:46 AM, Bernie Innocenti wrote:
> C. Scott Ananian wrote:
>> OK, thanks. The existing updater works fine in Debian; I don't know
>> if it was ever pushed into koji, but it is certainly compatible with
>> Fedora. If anyone wants to develop a new updater, I can probably
>>
On Mon, Feb 2, 2009 at 1:06 AM, Martin Langhoff
wrote:
> On Mon, Feb 2, 2009 at 6:38 PM, C. Scott Ananian wrote:
>> I still believe the proper way to do this is to have a local offline
>> cache. The protocol was explicitly designed to be easily cacheable.
>
> Because the use case looks like this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 02, 2009 at 10:46:35AM +0100, Bernie Innocenti wrote:
>C. Scott Ananian wrote:
>> OK, thanks. The existing updater works fine in Debian; I don't know
>> if it was ever pushed into koji, but it is certainly compatible with
>> Fedora.
Are
C. Scott Ananian wrote:
> OK, thanks. The existing updater works fine in Debian; I don't know
> if it was ever pushed into koji, but it is certainly compatible with
> Fedora. If anyone wants to develop a new updater, I can probably
> offer some advice. Using an explicit update_url field in the a
On Mon, Feb 2, 2009 at 6:38 PM, C. Scott Ananian wrote:
> I still believe the proper way to do this is to have a local offline
> cache. The protocol was explicitly designed to be easily cacheable.
Because the use case looks like this:
1 - the XS has no way to know what activities are on the XO
On Sun, Feb 1, 2009 at 9:24 PM, Martin Langhoff
wrote:
> So this depends on a simple service-announcement scheme. I'll sidestep
> the how of it, and say:
>
> When Sugar knows that there is a local "activity install/update"
> server, then the activity updater it _must_ try against the local
> servi
On Sun, Feb 1, 2009 at 1:47 PM, C. Scott Ananian wrote:
> offer some advice. Using an explicit update_url field in the activity
> is recommended for activities packaged with the current updater; the
> OLPC wiki default was only ever intended to be a bridge for legacy
> apps, not a recommended pra
On Sun, Feb 1, 2009 at 1:47 AM, C. Scott Ananian wrote:
> I prefer email for initial
> discussions of updater ideas: 9am isn't a great meeting time for me.
Email works fine for me. Bernie, you have been looking into the
updater code and discussed it with Tomeu and Michael already, could
you summa
On Sat, Jan 31, 2009 at 7:29 PM, Marco Pesenti Gritti
wrote:
> On Sun, Feb 1, 2009 at 1:26 AM, C. Scott Ananian wrote:
>> Can someone tell me what it is we are discussing?
>
> We need to integrate some kind of activity updating solution in
> Glucose. There is disagreement on when (0.84 or next re
On Sun, Feb 1, 2009 at 1:26 AM, C. Scott Ananian wrote:
> Can someone tell me what it is we are discussing?
We need to integrate some kind of activity updating solution in
Glucose. There is disagreement on when (0.84 or next release cycle)
and what (your updater, something based on it, a complete
On Sat, Jan 31, 2009 at 7:08 PM, Marco Pesenti Gritti
wrote:
> On Fri, Jan 30, 2009 at 9:54 PM, Michael Stone wrote:
>> Dear Sugar team,
>>
>> I've been very confused (and frankly, significantly angered) by recent
>> remarks
>> that I've encountered both in person (e.g. from Bernie) and in #suga
On Fri, Jan 30, 2009 at 9:54 PM, Michael Stone wrote:
> Dear Sugar team,
>
> I've been very confused (and frankly, significantly angered) by recent remarks
> that I've encountered both in person (e.g. from Bernie) and in #sugar (e.g.
> from Simon and Tomeu) about how sugar-related folk are thinkin
On Fri, Jan 30, 2009 at 3:54 PM, Michael Stone wrote:
> 2) Pursuant to the previous observation, I really think that various
> central people need to start doing their homework about what motivates
> their compatriots, what demotivates them, and (most relevant for the
> activity u
Dear Sugar team,
I've been very confused (and frankly, significantly angered) by recent remarks
that I've encountered both in person (e.g. from Bernie) and in #sugar (e.g.
from Simon and Tomeu) about how sugar-related folk are thinking about the issue
of mass activity installation and update. Cons
36 matches
Mail list logo
