I don't think Jacobson was suggesting that a really new paradigm in
networking would be able to handle the robust case of broadcast data, of
which unicasting is simply a subset. I find you need a little creativity
to fill in some of the gaps in the later part of the talk, since he
wasn't prese
Hi --
I'm new to the list though I have been on IRC now & then.
I loved Jacobson's talk but one point struck me: the introduction of a new
paradigm doesn't obviate the need for the old. Packet-switching is great
for fault-tolerance when the goal is "get this packet from here to there, no
matte
Lalo Martins wrote:
> On Wed, 09 May 2007 09:07:57 +0200, Karsten Otto wrote:
> > I don't quite understand what you need versioning for. The bulk of
> > changes you get in a shared word is avatar movement, which may wind up
> > to ~30 changes per second per avatar. Do you really want to keep a
> >
On Wed, 09 May 2007 09:07:57 +0200, Karsten Otto wrote:
> I don't quite understand what you need versioning for. The bulk of
> changes you get in a shared word is avatar movement, which may wind up
> to ~30 changes per second per avatar. Do you really want to keep a
> record of all this? My underst
> I don't quite understand what you need versioning for. The bulk of
> changes you get in a shared word is avatar movement, which may wind
> up to ~30 changes per second per avatar.
Nice question, there must be a control on what is covered by versioning.
It may be enough for some applications
I don't quite understand what you need versioning for. The bulk of
changes you get in a shared word is avatar movement, which may wind
up to ~30 changes per second per avatar. Do you really want to keep a
record of all this? My understanding was that if you want to make a
movie, its your re
Well, I was thinking that you have the (simplified) tuple (id, version).
You can't write to an older version, since that's rewriting history. The
kind of transparent branching like you're talking about seems a bit
excessive, although I was thinking about "alias" vobjects that would just
be a
> > This means that if that version object is mutable, i.e. a not read-only
> > property, we need to also have branches in the version history, and any
> > reference to a past version of a vobjcet is really a reference to "the
> > most recent version in the branch rooted on this object, which if th
On Tue, May 08, 2007 at 03:56:07PM -0400, Reed Hedges wrote:
>
> There are lots of ways to do version control in VOS-- we already have it
> partly implemented. One important thing that we need to decide is how
> to expose particular object revisions to remote sites. I think we need
> to be able to
There are lots of ways to do version control in VOS-- we already have it
partly implemented. One important thing that we need to decide is how
to expose particular object revisions to remote sites. I think we need
to be able to refer (by URL) to both the current version, or to any past
version (
10 matches
Mail list logo
