|
From: Bill B. <bb...@re...> - 2008-03-22 01:51:34
|
I did a big refactoring so that resteasy could support other HTTP servers. This expanded the SPI a little bit. I also had to refactor the testsuite a lot too. I also did some Grizzly HTTP and Grizzly Comet integration. Here are the details: * Grizzly HTTP Servlet was extremely buggy. I found and fixed 5 different bugs in their implementation by doing some delegation and inheritance hacks. * This implementation scares me because there is no testsuite for the Servlet stuff and only a tiny testsuite for the HTTP stuff. Its also totally hacked from the Tomcat codebase. * Grizzly Comet wasn't so buggy, but still had a few of the bugs I found in HTTP Servlet implementation that were related. * Both Grizzly HTTP and Comet take one full second to bootstrap. TJWS takes only a few milliseconds. So, TJWS is staying in. Full testsuite run with TJWS on my box: 7 seconds. Full testsuite run using Grizzly (HTTP or Comet): 30 seconds. I'm going to fool around a little bit with adding asynchronous capabilities to resteasy with Grizzly Comet. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |