gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Benja Fallenstein
Subject: Re: [Gzz-commits] gzz ./TODO doc/gzz.css doc/pegboard/.cvsignore ...
Date: Fri, 08 Nov 2002 14:39:08 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1

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. 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. If no Obs is passed, we return null but don't issue a notification if new data arrives. Same with links: If we don't know if the network has additional links, we return those we have and spawn a lookup process, triggering the Obs once we've found any.

- Benja





reply via email to

[Prev in Thread] Current Thread [Next in Thread]