Slashdot Mirror

← Back to Stories (view on slashdot.org)

Resin Released Under GPL

Posted by CowboyNeal on from the choices-are-good dept.

JohnA writes "I can't believe this hasn't received more attention than it has, but Caucho Software released their award-winning Java application server Resin under the GPL. This means that you are no longer bound to Tomcat and its less-than-stellar performance when deploying Java-based web apps."

9 of 50 comments (clear)

  1. Hmm... by klui · · Score: 4, Informative

    From 3.0.9's description:...

    "The Resin distribution for 3.0.9 has been refactored into two distributions:

    * Resin Professional - Most companies and organizations will use Resin Professional. Includes performance, caching, and clustering capabilities.
    * Resin Open Source (GPL) - Contains all functional components of Resin, including EJB, but excludes performance and clustering capabilities. "

    So, it looks like not all of Resin's performance is in the Open Source version. It would be interesting if someone were to compare the performance of Tomcat vs Resin Open Source.

    1. Re:Hmm... by zaqattack911 · · Score: 4, Informative

      Yeah I hate half assed gpl where they claim you're running a rechid turd of a server if you don't have the pro version.

      Clustering I can understand they don't include in the GPL version. But caching? doesn't tomcat at least do some caching.

      And what does "excludes performance" mean? wtf.. they took their mature software and "removed" performance from it? Sounds like BS.

      Maybe they just run a bunch of Thread.sleep() calls randomly in their code in the GPL version :)

      --Etan

  2. Who ever said Java was slow? by Johnny+Doughnuts · · Score: 4, Informative

    http://www.caucho.com/resin-3.0/features/jspvsperl php.xtp

    Keep this in mind when reading those benchmarks:

    The server is a 266 Mhz Pentium II running RedHat 6.0 with 64 meg of ram. The client is a 300 Mhz Celeron also running RedHat 6.0 with 32 meg. The two machines are connected with a 100bT ethernet connection.

    I'm considering deploying this on my person webserver now.

    1. Re:Who ever said Java was slow? by Kingpin · · Score: 2, Informative

      Those stats are for Resin 1.1 and JDK 1.1.8.. We're several generations down the road bub.

      --
      Unable to read configuration file '/bigassraid/htdig//conf/14229.conf'
      Geocrawler error message.
    2. Re:Who ever said Java was slow? by consumer · · Score: 2, Informative

      This benchmark is both ancient and wrong. I can't speak for the PHP code, but the mod_perl code is not done in the way that an experienced mod_perl programmer would do it, and thus does not demonstrate the best performance mod_perl can give in this situation. It would be better to look at this benchmark instead.

  3. I didn't think Tomcat was an app server... by BeatdownGeek · · Score: 5, Informative

    I didn't think Tomcat was really considered an app server, since Tomcat doesn't support EJBs. Tomcat is just a "Servlet/ JSP container," which JBoss happens to use now in its app server.

    Shouldn't this be compared to JBoss or Sun's app server (I forget what they call it)?

    1. Re:I didn't think Tomcat was an app server... by chickenwing · · Score: 2, Informative
      I don't think the definition of app server is "something that runs EJBs". You seem to be confusing one solution with a general concept.

      From The Free On-line Dictionary of Computing (27 SEP 03) [foldoc]:

      application server

      1. A {designer}'s or {developer}'s suite of {software} that helps {programmers} isolate the {business logic} in their {programs} from the {platform}-related code. {Application} {servers} can handle all of the {application} {logic} and {connectivity} found in {client-server} {applications}. Many {application} {servers} also offer features such as {transaction management}, {clustering} and {failover}, and {load balancing}; nearly all offer {ODBC} support.

      {Application} {servers} range from small {footprint}, web-based {processors} for intelligent appliances or remote {embedded} devices, to complete environments for assembling, deploying, and maintaining {scalable} {multi-tier} applications across an {enterprise}.
  4. Re:Tomcat catching up? by angel'o'sphere · · Score: 2, Informative

    The pre 4.0 versions of Tomcat where the so called "Servlet API reference implementations". Tehy where merly showcases how the specs are supposed to work.

    Tomcat is a serious Servlet engine since 4.1x and a pretty fast (more or less complete rewrite) since 5.0.

    As far as I know Tomcat 5.x is now in the top leage of server performance in serving static and dynamic content (faster than Apache).

    angel'o'sphere

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  5. Re:No JNDI ? by JohnA · · Score: 4, Informative

    JNI, not JNDI.

    Resin uses a custom JNI I/O library to increase performance. This component is not included in the GPL'ed version.

    Both releases allow JNDI.