JDH While it appears to be true that client-side Java generally sucks (i.e. writing UI intensive stand-alone applications) - it's too restrictive to say that Java is just for Web Apps. J2EE may not be a perfect framework (but there is no perfection in the field of engineering (it's all about compromise)) it really does offer a lot of benefits for server-side programming. OK, I know you're all groaning at me and thinking He has to say that he just got that new job I happen to think it's true. Honest! I even arrived at that opinion before applying for the job. It's just like most things in our field it's overhyped as a silver bullet - which ultimately causes as much bad press as it creates new sales. Now I suspect that DWM might have been using "Web Apps" as a shorthand for distributed applications (or a shorthand for something else?) but, seeing as we're trying to educate and elucidate here - let's make sure we don't cloud the issue with too many loose terms. ;-) I'm sure I'm guilty ;-) Anyway - I'll post more on this later (this new laptop is starting to burn a hole in my lap! ouch!)

DJH He ain't kidding. If you hold your hand over the QWERTY side it's very warm, but the numeric side (where the fan is) is reasonable.

I suggest asbestos Y-fronts.

Oh the irony of it!

So, what do you think one the first major problem that the EMS team is dealing with after my start with the team? In our by the numbers J2EE implementation? In our reference counted, garbage collected world? That's right - a freakin' memory leak! Of corse a garbage collector will only collect unreferenced objects and so it's pretty much just as easy to get resource leakage in the Java world if you keep creating and holding onto new referenced objects without letting go of your old references. Ho hum - it's out with the memory tracking tools! Don't laugh too hard and don't spread this around at work too much - but I just had to tell you all.