[cap-talk] choice of client-side for distributed application

[Stiegler, Marc D]

> > I think I need to get a web host that allows shell access, so I can 
> > run an E server (or a waterken server).
> 
> How about a CaPerl server?
> 
> http://caperl.links.org/

Hey, Ben, a CaPerl server that used the Waterken Server's YURL protocol
sounds like it would be really cool (said by a person who has never
written a word of Perl:-).

> > I do like the way that capabilities are passed around the network
> > with web-calculus.   If E makes that invisible, maybe I should
> > look at it more.   What is E's multiuser capability 
> distribution system?

E uses promise pipelining with the captp protocol. Read www.erights.org
and E in a Walnut for lots of explanations aimed at people with
different goals and mindsets.

> >
> > Have people deployed Elib clients with Java Web Start?  
> Does someone 
> > have an example?

JavaWebStart is just terrible. If I were to set out to prove that
fine-grain authority granting is unusable, I would invent JavaWebStart.
Apps under JavaWebStart hammer the user with dialog boxes requesting
authorities. Just write Java apps, not JavaWebStart apps.

--marcs