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.
In reply to Re: possible: a perl plugin for web browsers?
by vaevictus
in thread possible: a perl plugin for web browsers?
by drfrog
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |