You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2001/08/09 01:38:57 UTC

cvs commit: jakarta-turbine/notes NOTES

jvanzyl     01/08/08 16:38:57

  Modified:    notes    NOTES
  Log:
  - making some updates
  
  Revision  Changes    Path
  1.19      +0 -70     jakarta-turbine/notes/NOTES
  
  Index: NOTES
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine/notes/NOTES,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- NOTES	2001/07/18 17:57:57	1.18
  +++ NOTES	2001/08/08 23:38:56	1.19
  @@ -390,9 +390,6 @@
     
   o a proper caching service needs to be created
   
  -o add ObjectUtils methods to torque templates to decouple
  -  from turbine.
  -
   o turbine will consist of a set of components, it would be
     nice to have a notification system letting people know
     there are new pieces available and what the changes
  @@ -409,8 +406,6 @@
     
   o how to do site branding  
   
  -o JobEntry class is still dependent on the TurbineMapBuilder
  -
   o Lucene service
   
   o Slide service
  @@ -449,19 +444,10 @@
     Maybe PP could extend ExtendedProperties of a Configuration
     interface.
   
  -o While trying to move all the parser into the same package
  -  i see how couple all these things are. moving a couple
  -  classes broke way more code than i thought possible. yuck.
  -  Upon further looking, it was my import qualifier putting
  -  parent import references in the classes.
  -
   o the RunData/RunData service stuff has to be grouped
     better. maybe the ServerData class could be eliminated
     all together. get rid of all the object creation possible.
   
  -o get rid of as much object creation for a request as possible.
  -  ServerData immediately comes to mind.
  -
   o we need something that will tell us everything about an client.
     -> remove the localization service as all it does it tell us
        the locale of the user
  @@ -481,10 +467,6 @@
   o take the contents of HttpUtils and add them to RunData
     possibly. the caching methods at any rate.
   
  -o make proposals to get all our utility code in the
  -  commons. maybe an org.apache.commons.util package
  -  for file and string utils.
  -
   o need to find someone to work with who is willing to get
     the JSP service back up to the same level as the velocity
     service.
  @@ -496,18 +478,8 @@
     a portlet may be written with JSP or Velocity and we want
     the integration to work.
   
  -o totally remove ECS from the core. there is a file
  -  ecs.removal which outlines the classes that still require
  -  the use of ECS.
  -
  -o The Email class depends on TurbineResources and Criteria
  -  which is bad.
  -
   o think about the jars used:
   
  -  -> ECS is almost gone there are only 4 utility classes
  -     than we we will lose a 400k jar
  -     
     -> Xalan can probably be removed as it is only used for
        the XSLT service now so we should add detection for
        Xalan and remove it from CVS
  @@ -519,51 +491,9 @@
        of required jars but I would still like to clean up
        first.
        
  -o use the Digester for Torque schema files. this would reduce
  -  a ton of code from Torque. The Digester is very nice.
  -
  -
  -----------------------------------------------------------------
  -S E R V I C E  S E P A R A T I O N
  -----------------------------------------------------------------
  -
  -These are a list of files that still depend on Turbine
  -for configuration information.
  -
  --> localization stuff can probably be nuked and combined
  -   with other classes to make class to fully determine
  -   the capabilities of the client.
  -
  --> the security service should be entirely independent
  -
  --> rundata service is probably fine because it will
  -   always be a turbine service unless the rundata object
  -   is used in other webapp frameworks
  -
  --> I just nuked the substandard/useless LDAP security service
  -   from the repository. i could find something better in
  -   my cat's litter box. last time i'm convinced to put incomplete
  -   code into the repository by employees of startups.
  -
  -  localization/LocaleDetector.java:                Turbine.getConfiguration().getString("locale.default.language", "en"),
  -  localization/LocaleDetector.java:                Turbine.getConfiguration().getString("locale.default.country", "US"));
  -  localization/Localization.java:	String bundleName = Turbine.getConfiguration().getString("locale.default.bundle", "");
  -  pull/util/UIManager.java:        this.skinName = Turbine.getConfiguration().getString(SKIN_PROPERTY,
  -
  -  rundata/DefaultTurbineRunData.java:            String lang = Turbine.getConfiguration().getString("locale.default.language");
  -  rundata/DefaultTurbineRunData.java:            String country = Turbine.getConfiguration().getString("locale.default.country");
  -  rundata/DefaultTurbineRunData.java:            defaultCharSet = Turbine.getConfiguration().
  -
  ----
  -
   o replace the current cache service with either the code in the commons
     (which isn't documented very well, but look comprehensive) or the
     package from aaron smut's.
  -
  -o the velocity service is coupled to turbine because RunData
  -  is used directly to get the template encoding. We should modify
  -  the handleRequest method to take an optional encoding so that
  -  the application can provide it. in this case turbine.
   
   o how to make a general login action that can be used
     for all apps, what hooks could we provide to make it
  
  
  

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