in reply to When to use Java?

Most folks guessed you were talking about a CGI enviroment, but I refuse to make such an assumption, so i ask you, is that the case?

You say applet, so you're comparing a java applet to a perl/cgi program? (comparing clientside=java, to serverside=perl)

Please clairfy.

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: When to use Java?
by Willman023 (Scribe) on Nov 19, 2002 at 13:21 UTC
    Well, the assumption was correct. We are using CGI. But the problem is we use iPlanet webserver and I'm told mod_Perl is only supported on Apache. And I'm not sure about it being an applet, it is serverside Java so I guess its not.

    bW

      The problem here is not with Perl but with CGI. Your situation is comparing CGI to Servlets/JSP and the differences between the two mean that Servlets will normally win on performance.

      Mod_perl is for apache so yes, you won't get it to run on IPlanet. However, I think it is a little harsh to consider re-writing the whole app. Have you considered writing a middleware server that abstracts all your database code?

      That way you can keep a large majority of your existing database code (plus abstract your database from your view) and then just re-write your view? I've used this approach with great success here but, peversely, in reverse with a Java backend and Perl frontend. Just my 2p :)
      If you are using iPlanet on a Windows box then PerlEx may solve your problem with no recoding.. worth a look at least.

      Hope it helps
      UnderMine

      You might also want to take a look at CGI::Fast, PPerl and PersistentPerl - three alternatives to mod_perl for solving initialisation time issues.

      (mod_perl solves other problems too, but not relevant here :-)

      I work with bW......we are using java servlets on Iplanet.
      ---------------------------
      In closing, Screw Flanders.