commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [COMPRESS] COMPRESS-64 - enforcing correct sequence of API calls
Date Thu, 23 Apr 2009 12:04:31 GMT
On 23/04/2009, Christian Grobmeier <grobmeier@gmail.com> wrote:
> On Thu, Apr 23, 2009 at 1:49 PM, Torsten Curdt <tcurdt@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-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

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


Mime
View raw message