Re: [Gzz-commits] gzz ./TODO doc/gzz.css doc/pegboard/.cvsignore ...

[Tuomas Lukka]

On Fri, Nov 08, 2002 at 02:39:08PM +0100, Benja Fallenstein wrote:
> Tuomas Lukka wrote:
> 
> >On Thu, Nov 07, 2002 at 06:12:34PM +0100, Benja Fallenstein wrote:
> > 
> >
> >>Is this related to our IRC discussion about fetching Storm blocks 
> >>asynchronously, yesterday? So you mean doing an asynchronous network 
> >>lookup on xu links and trigger an Obs when new data arrives? That sounds 
> >>very good.
> >>   
> >>
> >
> >Well, actually both trigger an Obs but if Obs is null, just make note
> >that we'd like to know this at some point.
> >
> >I personally don't see as much use for the Obs as for just indicating
> >"get this when you have a chance, please" longer term, i.e. in a span
> >of weeks or even months.
> >
> 
> Sorry, but for "get this some time in the future" for now don't see any 
> use case at all. 

Let's say I have a *lot* of blocks on my hard drive and I'm on the train.
I start reading some stuff I haven't read before.

At that point, my system would make note of getting the related stuff
at some point.

> The interface I have in mind is like the spaces': 
> get(id, obs) returns a block if we currently have it, otherwise null; if 
> we don't have it we request it from the network, and if we can find it 
> there, we fire the Obs so that the views will get refreshed. 

Ah, we're thinking about different time spans. The views will be refreshed
every minute or so anyway.

        Tuomas