sorted by: recent | see :
popular
Content Tagged with Grizzly + General
T-Shirts, T-Shirts for sale...
Kohsuke just created a Cafe Press Store for Hudson and I just did a quick pass to collect those for other GlassFish friends; check them out:
|
• OpenPortal
|
There is also a
Grizzly
t-shirt
(I know because I'm the lucky owner of one)
but not (yet?) as a Cafe Press store,
and I'm chasing down shirts for
OpenESB,
OpenSSO
and
SailFin.
JRuby on Rails for the enterprise (with performance)
|
Recently voted Grizzly committer Naoto TAKAI had a presentation a couple of months ago at RubyKaigi2007. The slide deck is now available here. It mentions Grizzly on Rails (see the "Ruby and jRuby, Mogrel, Goldspike, Grizzly and GlassFish" earlier post), GlassFish v3 and some interesting benchmark numbers against Mongrel, GoldSpike and WEBrick. With the appropriate underlying technology, JRuby on Rails seems to be ready for the enterprise performance-wise. Service providers would be a good judge too. |
Prioritizing Ajax Request in GlassFish
|
If your site returns full web pages in a second or two, you probably have a bunch of happy users. But if your Ajax-intensive application takes a second or two for each small update to a page, your users may be calling for your head. No problem, you say, because your app handles its Ajax requests very quickly. But what happens when one of your Ajax requests get stuck behind slower non-Ajax requests in your webserver's queue? Lag. (And unruly users, in our example.) |
Fortunately, GlassFish provides a solution (with the help of its default network engine--Grizzly). Jean-Francois shows how you can use Grizzly's Resource Consumption Management extension to keep Ajax requests humming along with their own request queue and dedicated handler threads.
Of course, Ajax requests are just one example of traffic which you might want to prioritize with this technique. For more information on this and other advanced functionality in GlassFish, see the " Taste Special Features of Glassfish" lab from this year's JavaOne conference.
One TCP Port to Rule Them All
|
Grizzly is steadly being used by more and more components in GlassFish, and this is yielding a number of benefits. One is that it seems possible to service multiple protocols through the same TCP port. This is what JeanFrancois calls the Grizzly Port Unification mechanism. It is still early but we will soon find out how this can play in GlassFish v2. Check JFA's blog and this Discussion Thread. |