[cap-talk] capability based 3D whiteboard.
john.carlson3 at sbcglobal.net
Sun Feb 17 02:45:17 EST 2008
Say I want to implement a very simple line oriented network protocol
for a 3D whiteboard. An example of my protocol would look like this:
Groups are windows or tables or views or folders or directories of
points and polygons and groups. You can think of a polygon as an
ordered group. Points are regular files. Polygons inherit color and
position from points.
Basically, I would be using SQL like operators (CRUD) on points,
polygons and groups. Where should I add in capabilities if I want
people to have private groups, and be able to share groups? I am
hoping that Jed will see the similarity between GUI, DBMS and
Filesystems and realize he is an expert in all of them (not
withstanding the mindbending SQL requires).
Should I add COMMIT and ROLLBACK while I am at it? I already have a
form of rollback, because points keep track of their original locations.
More information about the cap-talk