On 23/04/2009, Christian Grobmeier <grobme...@gmail.com> wrote: > On Thu, Apr 23, 2009 at 1:49 PM, Torsten Curdt <tcu...@apache.org> wrote: > >> Similarly for other methods. The Abstract class would be responsible > >> for maintaining the current state and checking that the method is > >> valid for the state. > > > > Hm ... sounds a bit like overkill to me. > > > for me too.. I had this discussion long time back with Torsten, cause > the first drafts of compress had a similar approach. Meanwhile I share > his opinion.
Well, it may involve a bit more work now - which I don't mind doing - but adding a new archiver should be easier, as it would not have to do the state checking. The idea is to have the re-usable code in the abstract super-class. > Cheers, > > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
