hey
ok i do realize it has to be an
active x control for one browser!!lol

not everything i do is server side
the thing is its not about replacing a working solution,
its about having choices

sure java is great but have you ever had
to make an applet that worked:

a) on multiple o/s's?
b) on multiple browser and versions?
c) had to work on a java project with more than one class file?
d) had to recompile recompile recompile the java code?
e) had to use jar files that are out of date/have no source code?{ahhh cpan}


perl would eliviate a lot of this redundant work
and of course drive down the cost of the project too!!

look at my next post i wil be providing examples between the java and perl versions of eai
{i just wanted to address this post seperately}

back in the day we didnt have no old school