[2279] in java-interest
Re: Persistent Objects, Distributed Objects.
daemon@ATHENA.MIT.EDU (John Moore)
Wed Sep 27 19:37:42 1995
Date: Wed, 27 Sep 95 14:14:05 -0700
To: java-interest@java.sun.com
From: john@anasazi.com (John Moore)
Tom Judge writes...
>
>I'm just posting this as food for thought. How about extending
>Java so that is supports.
>
>1) Persistent objects. That is so that you can save an object
>instance and reload it from a URL. This would make back ends,
>databases etc. a piece of pie.
I'd like persistent objects on the Client, so you can create something with
an applet that can be used later on the client (on or off line). It should
have varying degrees of security so it can be shared with other applets, or
kept private, or only shared with certain applets (or classes, or whatever).
As a commercial example, imagine that you apply for an receive an electronic
credit card using the web and a Java-enabled browser. The credit card would
be a Java object that you get from the web site that issues it, and stores
itself on your machine. It is subsequently useable for electronic commerce.
Obviously authorization, permissions, authentication and other security
issues are critical here. For example... other authorized classes should be
able to use it. How do they get authorized? How are they authenticated? What
is the permissions scheme?
I see some very high volume important applications for this sort of thing in
the vertical market my company plays in.
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
