[5147] in java-interest
RE: Netscape security => lame applets
daemon@ATHENA.MIT.EDU (Pat Niemeyer)
Tue Jan 30 06:02:02 1996
Date: Tue, 30 Jan 1996 03:38:22 -0600 (CST)
From: Pat Niemeyer <pat@icon-stl.net>
To: Cay Horstmann <horstman@jupiter.SJSU.EDU>
cc: "'Nathan Williams <nathanw@MIT.EDU>'" <nathanw@jupiter.SJSU.EDU>,
"java-interest@java.sun.com" <java-interest@java.sun.com>
In-Reply-To: <01BAEE8F.BAA01FA0@mcsppp1.SJSU.EDU>
On Mon, 29 Jan 1996, Cay Horstmann wrote:
> Here is a better model. Distinguish between two kinds of applets. One kind
> can write back to the originating host but can only read from that host as
> well. Another kind can read from any host but can write nowhere. The latter
> kind would be my "information harvester".
>
> Right now I solved my problem by writing a CGI script. But it is a pain.
> You are certainly right that someone will come up with a way of making this
> all more transparent.
You could just make a simple proxy server and corresponding proxy
socket class that would make it all transparent. Of course there's
the question of whether you want to put restrictions on who can use the server
to do what, etc.
You could also serve your own protocol handlers that were identical to the
regular ones, but used your proxy sockets to read URLs.
Pat
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
