> I found this amusing: 'Every operation on an object must be > accompanied by a "capability," a cryptographically-signed ticket which > names the object and the access rights possessed by the owner of the > capability. In the absence of a suitable capability, the drive will > deny access. ' -- oh, and the objects are '2 64-bit numbers'. > > no assumptions about the network or protocol, eh?
i missed that part. (i also missed where they talk about who does the crypto and what protocols they will use.) this will make 9p latency look downright trivial. perhaps my brain went into self-protect mode. - erik
