Well... If you mean to add a single "plugin" where you could run perl scripts, as opposed to installing activeperl (for windows clients), if feasible, the plugin would be large.

Assuming that it was set up that way, we'd need to incorporate a GUI method for the webbrowser. Probably GTK or Glade or something, perhaps TCL/TK, which would morph into some sort of Browser::API; I'm not going into the holy war on GUIs thing.

After we had this "plugin" in place, we'd have to work on the transport protocol. It'd be a terrible thing to have someone insert into a cleartext transmission from a webserver to a perl plugin some malicious code like system("your nasty commandline here"); Which means we'd need at least a CRC transmission test system and probably SSL.

So... If we got the plugin created, and to an acceptible point where the clients would not have to worry about simple hack attacks, then we'd have something. I'm afraid I don't use much client side applications, so I don't use much java at all.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.