Hash: SHA1

Regarding the article linked to in the post Reed forwarded, in particular page five:

The discussion is how databases fit with the "lessons learned from the web". Since VOS is a database and access language of sorts, I'd like to respond to some of the points brought up in the article.

1. Are simple relaxed text formats and protocols supported?

Yes and no. At present, the XML message format has been retired in favor of an efficient binary format. It may one day stage a remarkable comeback, since XML-over-TCP is a hell of a lot easier for other people to interoperate with than Binary-over-VIP.

3. Do databases optimize caching when it is OK to be stale?

Caching is an important area which has yet to be addressed in VOS. The article makes an interesting point that when data is tagged with time-to-live information, it becomes much easier to determine what data changes infrequently and/or is permitted to be slightly out of date. This could be a useful feature to build into VOS, enabling prioritization in determining what elements of a local cache may or may not need to be updated. Certain scene elements such as texture data can be stale without causing any problems.

4. Do databases let schemas evolve for a set of items using a bottom-up consensus/tipping point?
5. Do databases handle flexible graphs (or trees) well?

In VOS, absolutely. These are both very basic design principals in VOS. Vobjects are easily evolved by attaching new vobject types, and building trees and graphs is the design purpose behind the parent-child relationship between vobjects.

[   Peter Amstutz   ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]  ]
[Lead Programmer][Interreality Project][Virtual Reality for the Internet]
[ VOS: Next Generation Internet Communication][ http://interreality.org ]
[ http://interreality.org/~tetron ][ pgpkey:  pgpkeys.mit.edu  18C21DF7 ]
Version: GnuPG v1.4.1 (GNU/Linux)


vos-d mailing list

Reply via email to