K
Kevin C.
I'm going to write a client-side web app that deals with local files. This
web app targets mainly public or corporate browser terminals. Normally I
would write an Applet because that's what I know (and because of Java's
extensive library of functions), but I've found that there are many
headaches dealing with Applets in that kind of environment. Not every IT
department installs the Sun JRE and it is usually difficult if not
impossible for the user to do so on that machine if doing so requires admin
priveleges. So I considered switching to JavaScript instead. However I am
wondering how difficult it is to implement file I/O in JavaScript, seeing as
to how the ECMA standard has no such provisions and the tutorials I've seen
on the web indicate that I/O exposure varies from one browser to the next.
If anyone out there has had experience with file I/O in this type of
environment, I'd like to know how much of a headache it is to use
JavaScript.
web app targets mainly public or corporate browser terminals. Normally I
would write an Applet because that's what I know (and because of Java's
extensive library of functions), but I've found that there are many
headaches dealing with Applets in that kind of environment. Not every IT
department installs the Sun JRE and it is usually difficult if not
impossible for the user to do so on that machine if doing so requires admin
priveleges. So I considered switching to JavaScript instead. However I am
wondering how difficult it is to implement file I/O in JavaScript, seeing as
to how the ECMA standard has no such provisions and the tutorials I've seen
on the web indicate that I/O exposure varies from one browser to the next.
If anyone out there has had experience with file I/O in this type of
environment, I'd like to know how much of a headache it is to use
JavaScript.