 |
Bye bye GlassFish, welcome grizzly.dev.java.net
Posted by jfarcand on February 06, 2007 at 01:19 PM | Comments (12)
Finally I've moved the Grizzly Framework 1.0.x out of GlassFish. I've got so many private emails on the topic I couldn't resist to start now instead of waiting for GlassFish v2 to go out! Starting now, all Grizzly development will happens outside GlassFish. The first module I've moved is the Framework classes. Next it will be the Grizzly HTTP WebServer. If you are interested to see what it looks (and even contribute to the code), just ask it here. I've refactored the 1.0 workspace and now every technology will have their own modules (grizzly-framework, grizzly-comet, grizzly-cometd, grizzly-jruby, etc.). Not to say that all the jars will be soon available inside the java.net repository. I've also migrated from Ant to Maven 2.0 for the build system, and from CVS to SVN. Much simpler! In case you can't wait for the Grizzly 1.5.0 official release, you can checkout the code by doing: % svn checkout https://www.dev.java.net/svn/grizzly
We will soon start discussing what Grizzly 2.0 will looks like, so join the mailing list if you want to collaborate. We (at Sun) are planning to consolidate all NIO implementation using Grizzly, hence this is the time to influence us!
technorati: grizzly comet cometd ajax/a> glassfish
Bookmark blog post: del.icio.us Digg DZone Furl Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
Some kind of continuations to extend and improve upon ARP. Basically, vacate pooled thread while waiting for remote service to respond. Remote service would need to execute some callback, of course, to notify that the job is done and request processing may continue. Any chance we would see that?
Posted by: denka on February 07, 2007 at 11:50 AM
-
Darn it, I could not un-mute myself during the User Experience conference, is it OK if I ask this question here?
Basically, what way is there to benefit from ARP in a rather standard case when a JSP is built of several Tiles, and each Tile may be involved in those long conversations with service endpoints?
Please suggest a different forum to discuss this if comments to this post are not an appropriate venue.
Thanks
Posted by: denka on February 07, 2007 at 12:50 PM
-
First question: Grizzly ARP is supporting that model. When a request is parked, no thread are associated with the parked request. You can see a very nice example (not written by me!) here. Thanks to Brian for that nice example!
Posted by: jfarcand on February 07, 2007 at 12:58 PM
-
Second question: LOL...*7 to unmute :-) I'm not an expert with Tiles, but this taglib most probably poll the server for content every time the page is requested . With ARP (or Comet), the Tiles implementation will only open a connection and wait for server push (not sure you can do that with Tiles....but you can with AJAX). At the user level it shouldn't make any difference, but internally the browser will open/close connection less frequently.
Posted by: jfarcand on February 07, 2007 at 01:03 PM
-
Tiles are just server-side includes, really. Fragments of a JSP taht is being rendered. The problem as I see it is that once you start rendering a JSP, you must grab a hold of a response and ARP is then impossible. Or is it?
Posted by: denka on February 07, 2007 at 01:18 PM
-
Yes it is. The reponse will be available as with the SRP (synchronous request processing) except the connection will not be closed and re-used to push more response. You can think of the server sending multiple response to as single request.
Posted by: jfarcand on February 07, 2007 at 01:53 PM
-
I saw in your slides for Grizzly 2.0 that you will be pulling away from dependencies on the glassfish container-- did I read this wrong in the context of the current version available or will we have to wait for 2.0?
Posted by: jhook on February 07, 2007 at 08:16 PM
-
Stll cannot see the grizzly 11 in maven?
Alors! Ben quoi alors?
Ludo
Posted by: ludo on February 08, 2007 at 07:40 AM
-
It seems java.net maven repository is having trouble. I've pushed the jar 3 times
[java] push-to-maven:
[java] [echo] importing to CVS...
[java] [cvs] Using cvs passfile: /home/ja120114/.cvspass
[java] [cvs] cvs server: Importing /cvs/glassfish/repo/grizzly
[java] [cvs] cvs server: Importing /cvs/glassfish/repo/grizzly/jars
[java] [cvs] N glassfish/repo/grizzly/jars/grizzly-1.0.11.jar
[java] [cvs] N glassfish/repo/grizzly/jars/grizzly-1.0.11.jar.md5
[java] [cvs] cvs server: Importing /cvs/glassfish/repo/grizzly/poms
[java] [cvs] N glassfish/repo/grizzly/poms/grizzly-1.0.11.pom
[java] [cvs] N glassfish/repo/grizzly/poms/grizzly-1.0.11.pom.md5
[java] [cvs] cvs server: Importing /cvs/glassfish/repo/grizzly/java-sources
[java] [cvs] N glassfish/repo/grizzly/java-sources/grizzly-1.0.11-sources.jar
[java] [cvs] N glassfish/repo/grizzly/java-sources/grizzly-1.0.11-sources.jar.md5 [java]
[java] [cvs] No conflicts created by this import
[java]
[java]
[java] BUILD SUCCESSFUL
[java] Total time: 21 seconds
BUILD SUCCESSFUL
Total time: 33 seconds
Finished at: Fri Feb 02 15:12:48 EST 2007
Will ping the admin
Posted by: jfarcand on February 08, 2007 at 07:50 AM
-
Jason, we have started migrating everything to the new workspace. Right now all the framework classes are available, next on my plate is to rebuild the Grizzly Web Server based on the new framework. It is not really new except there is new interface I need to implement. Then the JRuby/Comet/Cometd implementation will follow. We tagged the new version 1.5. Hence you don't have to wait for 2.0 if you want to use it :-)
Posted by: jfarcand on February 08, 2007 at 05:25 PM
-
Sorry if this is posted somewhere, but I'm looking for a project road-map or something that may tell me when the Grizzly 1.5.0 official release you mention will be generally available. I built from trunk last night and found that this version takes care of an issue I've had with 1.0.12. Thanks.
Posted by: kenny_stainback on March 02, 2007 at 06:08 AM
-
That's a good question. I would recommend you join the project so we can discuss with all the developpers the first official release on the mailling list. It should be in March, but we have to decide which features we want it.
Posted by: jfarcand on March 02, 2007 at 08:30 AM
|