+1 on deprecation

On Thu, 17 Mar 2005 09:28:00 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> The basic idea of catching ChainServlet up is sound, and I agree it
> should be done before the next release.  I'll be able to look at this,
> but not until tonight.
> 
> To reduce confusion, I'd also like to think about deprecating the
> original configuration mechanism (the one that preceeded
> CatalogFactory and supported only one catalog) -- although we'd still
> have to leave it in for backwards compatibility, of course.  What do
> you think?
> 
> Craig
> 
> 
> On Thu, 17 Mar 2005 05:59:50 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote:
> > At 11:21 PM -0800 3/16/05, Craig McClanahan wrote:
> > >I'm fine with a 1.1 designation (there is a quite useful enhancement
> > >here) and will review the code and docs tomorrow for any useful
> > >updates.
> >
> > Craig, maybe you can have a look at
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=34022
> >
> > It was a response to Howard Lin's questions last week about using
> > ChainProcessor.  As I got deeper into the code, the problem looked
> > less dire than I had thought, but I was leary about committing the
> > changes without some attention from someone who had either used the
> > ChainProcessor or who was in a better position to test them out.
> >
> > All of the other[chain] tickets in Bugzilla are enhancements.
> >
> > Joe
> >
> > --
> > Joe Germuska
> > [EMAIL PROTECTED]
> > http://blog.germuska.com
> > "Narrow minds are weapons made for mass destruction"  -The Ex
> >
> > ---------------------------------------------------------------------
> > 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]
> 
>

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

Reply via email to