Re: JavaScript Compression

["Peter Connell" <Peter.Connell@xxxxxxxxxxxxxxxxx>]

The MicroSoft routine did a pretty good job in my book.
The javascript was responsible for emulating the Basic Authentication
log in dialogue which I needed to hijack for some reason that eludes me
now (maybe something to do with the 3 attempt thing or password expiry)
The code delivered to the browser was so unreadable that it would
disuade hackers.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Nathan Andelin
Sent: Wednesday, 12 March 2008 4:21 p.m.
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] JavaScript Compression


> Peter Connell wrote:
> I have always presumed that browser caching helps avoid
> some of the problems with lots of JavaScript.

Browser cache does help a lot.  I'm not sure what the algorithm is to 
request a refresh of the file.  Mostly, I've noticed that when a 
JavaScript file is changed, the browser normally get's the new code.  It

appears that the browser at least checks to see if a file has changed. 
Ocasionally I have to clear browser cache to see the changes.

But compressing files saves a little bandwidth, which I think is helpful

as I've gravitated toward writing more JavaScript.  Any further thoughts

on obfuscation?

Nathan.