I think it's been long enough, I plan on renaming "Fast*" to "Async*"
Gary On Mon, Jul 22, 2013 at 3:54 PM, Gary Gregory <[email protected]>wrote: > A JIRA is tracking the list of new candidate class names. > > Gary > > > On Mon, Jul 22, 2013 at 2:47 PM, Paul Benedict <[email protected]>wrote: > >> Was there any conclusion to this? >> >> >> On Fri, Jul 19, 2013 at 12:11 PM, Paul Benedict <[email protected]>wrote: >> >>> Being in the dark here, is there any reason to provide a non-fast >>> version? I only ask because FastDateFormat makes sense in that it is a >>> replacement for a JDK counterpart. Is the FastFileAppender a replacement >>> too? If not, I say why not only provide the fast one? >>> >>> >>> On Fri, Jul 19, 2013 at 12:02 PM, Remko Popma <[email protected]> wrote: >>> >>>> It's faster than FileAppender. >>>> >>>> http://logging.apache.org/log4j/2.x/manual/async.html#FileAppender_vs._FastFileAppender >>>> >>>> >>>> ------------------------------ >>>> *From:* Paul Benedict <[email protected]> >>>> *To:* Log4J Developers List <[email protected]> >>>> *Sent:* Friday, July 19, 2013 11:20 PM >>>> *Subject:* Re: Rename FastFileAppender >>>> >>>> I'd like to know what it's faster than too. The only other "fast" class >>>> is Commons Lang FastDateFormat. In their javadoc they say: "FastDateFormat >>>> is a fast and thread-safe version of SimpleDateFormat." I think the >>>> inference (taking a guess here) is that it's faster than SimpleDateFormat. >>>> >>>> I agree with Gary. Unless we have a comparison to something else, I say >>>> the "fast" adjective is meaningless. >>>> >>>> >>>> On Fri, Jul 19, 2013 at 8:26 AM, Gary Gregory >>>> <[email protected]>wrote: >>>> >>>> Hi All: >>>> >>>> This came up before but recent emails reminds me that we should rename >>>> FastFileAppender >>>> and related classes to better names since "Fast" begs the question: Faster >>>> than what? And: Where is the SlowFileAppender, and MediumSpeedFileAppender >>>> and so on, you get the idea. >>>> >>>> I think the name that floated up before is >>>> RandomAccessFileAppender. >>>> >>>> (Alternatively but not my 1st choice: RAFAppender, RafAppender.) >>>> >>>> Thoughts? >>>> >>>> Then both RandomAccessFileAppender and FileAppender co-exist until we >>>> decide to: keep both or pick one as the true FileAppender. >>>> >>>> Gary >>>> >>>> -- >>>> E-Mail: [email protected] | [email protected] >>>> Java Persistence with Hibernate, Second >>>> Edition<http://www.manning.com/bauer3/> >>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >>>> Spring Batch in Action <http://www.manning.com/templier/> >>>> Blog: http://garygregory.wordpress.com >>>> Home: http://garygregory.com/ >>>> Tweet! http://twitter.com/GaryGregory >>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Paul >>>> >>>> >>>> >>> >>> >>> -- >>> Cheers, >>> Paul >>> >> >> >> >> -- >> Cheers, >> Paul >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
