[cap-talk] top-to-bottom (cajaDesk at the top?)

[Stiegler, Marc D]

Yes, that would be very cool. You could then run CajaDesk on Tahoe. You would still need the CajaBrowser to be able to interact with a local server of some sort, however, if you wanted to use authorities from more than one site. The Tahoe site is one of the more interesting sites, but not the only interesting site, to have a cajoled application compose authorities from. Unless the Taho guys would like to run a suitable webkey message forwarding server as part of their offering. Then any authority on any site that has been suitably wrapped with a webkey protocol becomes fair game. Zooko, Brian, how does that sound as a Tahoe extension? :-)

--marcs 

> -----Original Message-----
> From: cap-talk-bounces at mail.eros-os.org 
> [mailto:cap-talk-bounces at mail.eros-os.org] On Behalf Of Toby Murray
> Sent: Wednesday, January 14, 2009 11:35 AM
> To: General discussions concerning capability systems.
> Subject: Re: [cap-talk] top-to-bottom (cajaDesk at the top?)
> 
> On Wed, 2009-01-14 at 18:55 +0000, Stiegler, Marc D wrote:
> > The important issue to remember is that the authorities a 
> Caja "desktop" would be in position to use would are not the 
> traditional desktop authorities, which makes it harder to 
> determine what it means to be a "desktop". For example, Caja 
> in a browser can't manage file authorities because it can't 
> reach file authorities at all. And Caja unchained from a 
> browser doesn't have a tamed library for accessing files, so 
> that is a block of work you'd need to do.
> 
> One could easily imagine Caja code with Tahoe URLs. These are 
> authorities to files and directories. A Caja library that 
> allowed asynchronous Tahoe interaction would be useful here.
> 
> 
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>