in reply to Re^2: How to answer "Perl is not secure" objections?
in thread How to answer "Perl is not secure" objections?
While we are on the subject, of a "Perl browser plugin" , like the libjavaplugin_oji.so in our browser's plugin directory; what has stopped the Perl developers from doing this? From my limited understanding, the java plugin is just a java interpreter with the functions which pose a security risk removed, leaving only simple computational and display functions, and which limits display in the parent's (browser's) allocated window.
I'm not really a human, but I play one on earth. Cogito ergo sum a bum
When I build Perl, I see the mini and micro Perl interpreters, which are limited versions. Would it be that hard to modify those to be a secure browser plugin? Then maybe add a chopped-down Tk or Gtk2 display engine to it? Now I wish I studied c in more depth. :-)
I'm not really a human, but I play one on earth. Cogito ergo sum a bum
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: How to answer "Perl is not secure" objections?
by mr_mischief (Monsignor) on Sep 07, 2007 at 14:47 UTC |
In Section
Seekers of Perl Wisdom