GlassFish V3 Grizzly One Pager [
Unknown macro: {TableOfContents title=' '}
|(TableOfContentstitle='')] 1. Introduction 1.1. Project/Component Working Name: Grizzly 1.2. Name(s) and e-mail address of Document Author(s)/Supplier: Oleksiy.Stashok@sun.com, Jeanfrancois.Arcand@sun.com 1.3. Date of This Document: 15/12/08 2. Project Summary 2.1. Project Description: Project Grizzly is networking framework based on NIO, which helps developers to build scalable and robust servers using NIO and also offering embeddable components supporting HTTP, Bayeux Protocol, Servlet (Partially) and Comet. Grizzly serves as network layer for Glassfish v3 and is embedded to its core. It takes part in making decision to which App server component (Web tier, EJB etc) an incoming request should be passed to. All the network communications in Glassfish V3 are passing throw Grizzly. 2.2. Risks and Assumptions: Note any risks, and assumptions that must be considered along with the proposal. Include technical risks. 3. Problem Summary 3.1. Problem Area: Network communications. Implementation of scalable and performant servers. 3.2. Justification: Network layer performance has sensitive influence on overall app server performance. Using Grizzly, Glassfish v3 gets performant, scalable and extensible network layer, which lets Glassfish components easily link up to network communications. 4. Technical Description: 4.1. Details: Grizzly is open source project. It is implemented on top of Java NIO. We also follow NIO.2 or AIO specification, which will become available with JDK 7. 4.2. Bug/RFE Number(s): 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: 4.5.1 Exported Interfaces Disclose all interfaces that this project exports.
4.5.2 Imported interfaces Disclose interfaces this project imports.
Interface |
Stability |
Former Stability (if changing) |
Comments |
Java NIO |
Stable |
|
API bundled with JDK |
ExecutorService |
Stable |
|
Thread pool API bundled with JDK |
4.5.3 Other interfaces (Optional) 4.6. Doc Impact: 4.7. Admin/Config Impact: We're going to implement Grizzly config, which will have impact on domain.xml configuration. 4.8. HA Impact: No. 4.9. I18N/L10N Impact: No. 4.10. Packaging & Delivery: Currently required Grizzly modules are bundled together inside special Glassfish module. We plan to bundle Grizzly directly using OSGi. 4.11. Security Impact: Grizzly uses domain.xml attributes and properties to setup SSL support, if required. 4.12. Compatibility Impact No. 4.13. Dependencies: Optionally Grizzly config 5. Reference Documents: 6. Schedule: 6.1. Projected Availability: Latest release: Grizzly 1.9.1 (is already integrated to GFv3)
|