> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, March 13, 2003 11:21 AM
> To: [EMAIL PROTECTED]
> Subject: Classes to go post Turbine-2.3-dev
> 
> 
> Hi,
> 
> the following classes from Turbine-2.3-dev I'd like to see go 
> after 2.3:
> 
> 
> org.apache.java.lang.Bytes
> org.apache.java.security.MD5 org.apache.java.security.MessageDigest
> 
> used in 
> 
> org.apache.turbine.services.uniqueid.TurbineUniqueIdService.java
> org.apache.turbine.util.db.UUIdGenerator.java
> 
> No replacement for these in any commons yet. Solution: Either 
> remove the whole Unique Id Service, rewrite it using standard 
> classes or lobby these o.a.java classes into commons components.

Rewrite using RandomStringUtils from commons-lang.  Perhaps a milliseond
counter to the end of the id to ensure that it will be unique.

> In  org.apache.turbine.util we have
> 
> Name                  Possible Replacement
> 
> BrowserDetector               commons-sandbox/http/BrowserDetector
> FileUtils             commons-sandbox/io/FileUtils
> HttpUtils             commons-sandbox/http/HttpUtils
> ObjectUtils           commons/lang/ObjectUtils
>                       (check for stuff like addOnce!)
> SequencedHashtable    commons/collections/SequencedHashMap
> StringUtils           commons/lang/StringUtils

+1 so far
 
> FormMessage             used only in one place in RunData. 
> Can we remove
> FormMessages            that?

I think this would mainly be accessed in templates.  I use
RunData.setMessage() to send information back to the view....  This
probabley needs to stay.  That is assuming that the getMessage()
setMessage() and hasMessage() uses FormMessage.
 
> GenerateUniqueId        Seems to be part of the UniqueId 
> Service. Maybe move
>                         there

Kill it.  See my prior comments about the unique id service.

> SystemError           Used only in Intake and at one point in RunData
>                         How about removing and replaceing 
> with TurbineException

Maybe create a TurbineError to replace it.  I can't think of anything in
RunData or Intake that would ever need to throw an Error though.
 
> StringStackBuffer     no replacement, should go collections?
> QuickSort             no replacement, should go lang / collections?
> Comparable              helper for Quicksort

+1

> CookieParser          should move into utils.parser 
> CSVParser
> DataStreamParser
> ParameterParser
> TSVParser
> ValueParser

+1
 
> Any opinions about this?
> 
>       Regards
>               Henning
> 
> 
> -- 
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
> [EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/
> 
> Java, perl, Solaris, Linux, xSP Consulting, Web Services 
> freelance consultant -- Jakarta Turbine Development  -- hero for hire
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to