[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: you don't have to ask, but you'll be sorry you didn't
Generally an applet is sent from the server to the client. The
client does the actual work and then destroys the applet when
finished. It the case of an applet that is sent to the client I'd
bet that it is exported when the page is accessed by someone
offshore. Or at least that would be how I'd intrepret it if on a
If all the work was done on the server as Kevlar wrote I'd say that
nothing was exported except a bunch of random looking bits.
At 1:00 PM -0800 2/01/99, Kevlar wrote:
> Don't quote me on this, but it's my understanding that it's the code that
> does the work, not the result of the work that's controled by export
> laws... In your example (as I understand it) all the work is done on the
> server side (like when a perl or asp script is executed), and just the
> results are fed "overseas"....
> Now, in the case of a ftp site that has pgp.exe or something like that,
> then yes, which is why there are so many steps to downloading pgp.
> Correct me if I'm wrong...
> At 12:24 PM 2/1/99 -0800, you wrote:
>>Am I right in assuming that an applet that performs non-exportable
>>encryption is considered to have been exported when the page is accessed
>>by someone offshore?