(Cutting the great summary, keeping the VOS part)
On Mon, 07 May 2007 22:57:05 -0400, Peter Amstutz wrote:
> So, Lalo, this is probably a bit more than you expected :-) I think the
> answer to your question ("could VOS be useful for the things Van
> Jacobson talks about") is yes, if we incorporate a robust notion of time
> and version as related to state changes. If anyone thinks this is
> fanciful, this actually cuts right to the core of how remote vobjects
> work, and how we eventually handle caching -- central issues to the s5
> redesign.
The gratifying thing is that we already talked about this sort of thing
before, and I think the ideas we reached then are still perfectly valid
in this context.
I was thinking earlier this week about version-control-like updates; in
cases where you know sending a whole tree of vobjects is expensive, and
that it typically doesn't update much (or rather, most updates affect
only the same small subset of objects). Then we go in an approach
similar to bzr (or svn); we send our last-seen revision, the server
computes a "patch" and sends it back. (That's just the tip of the
iceberg; this raises questions of storage space, which are answered with
horizons, which raises other questions and so on...)
best,
Lalo Martins
--
So many of our dreams at first seem impossible,
then they seem improbable, and then, when we
summon the will, they soon become inevitable.
-----
personal: http://lalo.hystericalraisins.net/
technical: http://www.hystericalraisins.net/
GNU: never give up freedom http://www.gnu.org/
_______________________________________________
vos-d mailing list
[email protected]
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
