Table of Contents
1. Introduction

1.1 Project/Component Working Name
1.2 Name(s) and e-mail address of Document Author(s)/Supplier
1.3. Date of This Document

2. Project Summary

2.1 Project Description
2.2 Risks and Assumptions

3. Problem Summary

3.1 Problem Area
3.2 Justification

4. Technical Description

4.1 Details
4.2 Bugs/RFE's
4.3 Scope
4.4 Out-of-scope
4.5 Interfaces
4.6 Documentation Impact
4.7 Configuration/administration Impact
4.8 High Availability Impact
4.9 Internationalization
4.10 Packaging
4.11 Security Impact
4.12 Compatibility
4.12 Dependencies

5. References
6. Schedule

1. Introduction

1.1. Project/Component Working Name

Grizzly V2

1.2. Name(s) and e-mail address of Document Author(s)/Supplier

Charlie Hunt : charlie.hunt@sun.com

Jeanfrancois Arcand : jeanfrancois.arcand@sun.com

1.3. Date of This Document

08/21/06

2. Project Summary

2.1. Project Description

This project pulls the high performance transport components from the existing Grizzly HTTP Connector and places them in a shared jar where other components of GlassFish requiring a high performance transport can utilize those components such as; GlassFish ORB and GlassFish MQ.

2.2. Risks and Assumptions

As for any project, schedule and resourcing risks exist for this project.

3. Problem Summary

3.1. Problem Area

This project will provide the same high performance transport enjoyed by Grizzly HTTP Connector to GlassFish ORB and in the future to GlassFish MQ. Additionally, this project paves the way for a future feature called “Port Unification”.

3.2. Justification

This is a project which will improve GlassFish performance.

Additional benefits include; utilizing the same source code across multiple functional areas reduces duplication of effort, duplication of similar source code, allows each functional area to leverage a known high speed transport which already exists in Grizzly HTTP Connector along with GlassFish download size, and GlassFish runtime footprint size. In addition, implementing a performant high speed transport using Java NIO is difficult. Hence, the probability of having one functional area with a poor performing implemention is higher if all functional areas develop their own transport. Also, having Grizzly HTTP Connector, GlassFish and GlassFish MQ all using the same high speed transport source code is the first step towards being able to provide a solution for “Port Unification”.

4. Technical Description

4.1. Details

This project will be implemented by Charlie Hunt and Jeanfrancois Arcand, key players in the implementation Grizzly HTTP Connector, by pulling the high performance transport pieces of Grizzly HTTP Connector into a separate jar which will be delivered to GlassFish and utilized initially by Grizzly HTTP Connector and GlassFish ORB. In a future release, GlassFish MQ will migrate their implementation to utilizing the same shared Grizzly jar files.

4.2. Bug/RFE Number(s)

This project is critical to improving performance of GlassFish.

4.3. In Scope

4.4. Out of Scope

4.5. Interfaces

Interfaces developed as part of Grizzly V2 will be utilized internally by Grizzly HTTP Connector and GlassFish ORB initially, eventually by GlassFish MQ. However, it conceivable these interfaces could be used by external GlassFish projects.

4.5.1 Exported Interfaces

Grizzly V2 interfaces are under develop at the time of this writing and subject to change.

Interface

Stability

Former Stability (if changing)

Comments

4.5.2 Imported interfaces

This project depends on the interfaces exposed by Java SE NIO package and Java SE 5 language features, (generics, java.util.concurrent, java.util.concurrent.atomic and java.util.concurrent.locks packages).

4.5.3 Other interfaces (Optional)

No imact.

4.6. Doc Impact

No impact.

4.7. Admin/Config Impact

No impact.

4.8. HA Impact

No impact.

4.9. I18N/L10N Impactinks

No impact.

4.10. Packaging & Delivery

No known impact.

4.11. Security Impact

No known impact.

4.12. Compatibility Impact

No impact.

4.13. Dependencies

No dependencies.

5. Reference Documents

6. Schedule

6.1. Projected Availability

Grizzly V2 Implemented, roughly late August 2006

Grizzly V2 integrated with Grizzly HTTP Connector, roughly late August 2006 / early September 2006

Grizzly V2 integrated with GlassFish ORB, roughly mid late September 2006