[cap-talk] Creating 32-bit capabilities, automatic capabilities by subclassing?

[Sandro Magi]

John Carlson wrote:
>> A YURL is just a regular URL, with the added property that it's
>> unguessable. This additional property means it can be be used as a
>> capability, aka a secure object reference.
> 
> What I mean was, is this a creational YURL, an object YURL,
> a method YURL, an attachment YURL, etc. etc. 

Any of the above.

> Can the
> client figure out what to do with the YURL if passed one through
> a 3rd party, or through some queue supported by Waterken Server?

Performing a GET on the YURL returns an XML description of the
interface. The client, whether it be a browser or software agent, can
figure out what to do then.

Sandro

> I'm not talking about plugging a YURL into a web browser,  I want
> that information as part of client software.
> 
> One thing I suppose I could do is generate X3D using a stylesheet
> associated with code on the server.   This certainly is a possibility.
> I would probably have to write an X3D fragment parser on the client
> side.  I am not sure, but I think that most X3D parsers parse entire
> documents.  I guess I can look for streaming X3D.
> 
> John
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk