[cap-talk] Network POLA

[John Carlson]

On Jun 5, 2006, at 7:15 PM, Jed at Webstart wrote:
> What's really
> needed is a practical path to change the basic authority paradigm
> for computing.  To me starting at the level of the network is the best
> hope.

I think we should think about working on multiuser database systems that
work across the network.   Simple Create, Read, Update, Delete,  
Triggers, Grant
and Revoke, of any object on the server.   This would solve both
the message queuing (chatting and exchanging messages and capabilities)
and the shared workspace problems (whiteboards, wikis, etc).  I would
assume that if a client wanted to do some kind of complex join, this
could be done on the client side.

What I am torn about is whether to provide a generic facility on
the server, which any customer client can use, or to customize the
server on a per application basis.  Perhaps we can do both
at the same time.

In any case, I think that quotas are necessary in order to prevent
"accidental" DoS attacks.  Thus someone might have limits
on the number of objects they can create, and other scarce
resources.

Could I potentially send a class definition to waterken through
a post, so that waterken would gain knowledge of that class?
I can see how prototype inheritance would come in useful
here.

So in OO terms, would we need the following classes:

Creating
Reading
Updating
Deleting
Granting
Revoking (like deleting)
Conditional Procedure
more?

Note that Granting is done by sending YURLs to the client.
I am not referring to your typical database grant/revoke


John