commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-commons Wiki] Update of "PoolRoadMap" by SandyMcArthur
Date Sun, 05 Mar 2006 04:40:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by SandyMcArthur:
http://wiki.apache.org/jakarta-commons/PoolRoadMap

The comment on the change is:
updated road map with what I understand the current plans to be

------------------------------------------------------------------------------
  
  == Releases ==
  
- === Pool 1.3? ===
+ === Pool 1.3 ===
  
- There are a number of important fixes which have been committed. Therefore, cutting a 1.3
release may make sense.
+ There are a number of important fixes which have been committed. Therefore, cutting a 1.3
release makes sense.
  
  === Pool 2 ===
  
- This will not fully compatible with the Pool 1.x releases. This has been necessitated by
some recent changes to semantics. This offers a change to break binary compatibility as well
(if necessary).
+ This will not fully compatible with the Pool 1.x releases. This has been necessitated by
some recent changes to semantics. Areas with the code contracts defined in interfaces is loosely
defined or unnecessary allows methods to return a variety of responses with the same meaning
will be changed to more user friendly behavior. This release will take advantage of Java 1.4
features.
+ 
+ === Pool 3 ===
+ 
+ This may break API compatibility for implementations of pools but shouldn't affect client
code using pools. Mostly the exceptions declared in the interfaces that is no longer needed
because of behavior changes in Pool 2 will be removed. This release probably will take advantage
of Java 5 (aka: 1.5) features.
  
  == Performant Implementations ==
  
- The current implementations concentrate on stability and robustness rather than performance.
It may be possible to create new, more performant implementations. This depends on developers
stepping up.
+ The current implementations concentrate on stability and robustness rather than performance.
Pool 2 will introduce new implementations geared towards performance.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message