Hi Antonio,
On Tue, Aug 27, 2002 at 07:34:49PM -0600, Antonio Gallardo Rivera wrote:
> Reason 1:
>
> What kind of security concerns? You can tell the browser what the script can
> do. Please explain more. Perl can have "security concerns too". Do you know
> that?
the number of security problems in Perl - viewed over the years - is
much less than the number of security problems in ECMAScript (as is
the official name for this misbegotten pseudo language). Here I'm not
talking about a specific application or library, but about the core
where Perl does a very good job of containing any risks ("-T") while
JS implementations are apparently often enough done with a hot needle.
Recently I also worked on a web project that should have involved
using DHTML, but that was at last dropped because it turned out that
all available code either weren't suitable and robust enough, or
had to be licenced for a (hefty) fee, and also were largely unsupported
by their respective developers. I've yet to encounter such problems
in the Perl arena. Same story in short: Developing DHTML is MUCH MUCH
more expensive than developing an "ordinary" web application, also
with respect to maintenance cost.
If you are so badly after a "nice" user interface, please consider
any of the following options (I gather that you don't have security
problems in the first place):
- Try to get the user to download a Perl or TCL/Tk plugin, and load
the application over the 'Net.
- Give them "shell" access and allow them to run the Perl/Tk version
instead of the browser version.
If you really argue that users can adjust what the JS engine in their
browsers can do, you are also saying:
- Your users are very much above the usual "user" standard in savviness.
- Your users are still too dumb to use the current web or Tk interface.
You will run into severe compatibility problems the more you rely on
JS because tomorrow's version of your favourite browser will have more
controls on what specifically to disable, and your interface will
require exactly this feature to be on (eg. I found sites that rely on
reading a cookie using JS for no good reason, imho).
You also have the option of doing the JS interface yourself...
> Reason 2:
> Please tell me what "relevant" browser dont support it. I use Mozilla,
> Konqueror, Galeon, Internet Explore and Netscape and ALL support it. Then I
> dont know what you use.
Yesterday I tried w3m (a fine text mode browser). Unfortunately, it
doesn't work, although it should be a minor issue with a MIME type
(application/x-perl).
> Is very easy tell this too reasons, please be more explicit.
Done.
Best,
--Toni++
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
-------------------------------------------------------
(un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users
Archive: http://www.mail-archive.com/[email protected]/
