We've been doing stuff like this for quite some time now, mostly to compress
data transfered from the client to the server using the GZIP stuff in java.
It's never been a problem for us. In fact if you make use of the innerHTML
and innerText stuff, and use an applet to do the communication to the
server, you can have forms that operate without having to ever even reload
the page, kinda cool, but it's IE only for most of this stuff (and then you
can just use an HTTPRequest object and skip the applet altogether). Anyways,
hope this helps.

Jordan Frank
jfrankb-ap.com

----- Original Message -----
From: "Voodoo Child" <auto125268HUSHMAIL.COM>
To: <WWW-MOBILE-CODESECURITYFOCUS.COM>
Sent: Monday, April 23, 2001 11:03 AM
Subject: Preventing Browser Residue

> A site I am working on is about to start selling stuff and we need to be
> able to show an account number (biz req, no way around). I have been
really
> careful when looking at forms using POST and nt GET and what else gets
rendered
> to the screen, no-cache options etc but still account numbers can get
cached
> in the browser.
>
> So I came up with an idea, how about using an applet to take in an object
> as a variable. The applet can communicate back to the original server (ok
> in Java model) ? Any thoughts, is this mad ?
> Free, encrypted, secure Web-based email at www.hushmail.com

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]