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

[John Carlson]

>
> If you want to stick with Java, you could make use of the underlying
> libraries on which E is implemented: ELib. They're written in Java and
> might get you a long way towards your goal of a distributed
> capability-based whiteboard system.

I think I need to get a web host that allows shell access, so I can
run an E server (or a waterken server).  Right now, I am limited to
Perl and PHP.   Thus this whole conversation is kind of moot until
I can get a reasonable web host.  What I am trying to to do is to
get someone to host a generic capability server that I can use as
a database to support various applications.  I can help design
such a server.  It's a long term goal--I don't have any immediate
need for this.  If people do have a need for such a server, we should
start designing this on some mailing list somewhere.  Perhaps someone
would be kind enough to donate a server for this effort?  If I were
to start such a project, what would be a good name for it?

I feel that we can take two approaches.  Try to design something
that will host any capability database application w/o implementing any
client specifics on the server (unless they are uploaded somehow).
Or we can continue along the lines of waterken, and do server
extensions.  I can see giving clients a capability to upload an
application or class into the server, and have it run in a sandbox.
Perhaps one can send a collection of classes that all run in the
same sandbox.

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?

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

John