You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Gilles Scokart <gs...@gmail.com> on 2007/05/14 19:43:56 UTC

Ivy class : Temproary or definitive facade

What was the intention (and what is the intention now) of the Ivy facade.

Is it the single entry point by design and it should stay like that.
Or is it there for historical reasons and it is suposed to be
'bypassed' progessivley.

More particularily.  I'm currently writing/updating some test for the
sort algorithm.  The tests currently invokes the Ivy class as it is
the single entry point.  If the ivy class is suposed to be bypassed
and the code will progressively use the SortEngine directly, then the
"unit-test" should probably already target directly the SortEngine.

WDYT

-- 
Gilles SCOKART

Re: Ivy class : Temproary or definitive facade

Posted by Xavier Hanin <xa...@gmail.com>.
On 5/14/07, Gilles Scokart <gs...@gmail.com> wrote:
>
> What was the intention (and what is the intention now) of the Ivy facade.
>
> Is it the single entry point by design and it should stay like that.
> Or is it there for historical reasons and it is suposed to be
> 'bypassed' progessivley.
>
> More particularily.  I'm currently writing/updating some test for the
> sort algorithm.  The tests currently invokes the Ivy class as it is
> the single entry point.  If the ivy class is suposed to be bypassed
> and the code will progressively use the SortEngine directly, then the
> "unit-test" should probably already target directly the SortEngine.
>
> WDYT


I think the unit test can target the SortEngine directly, they are unit
tests anyway.

For the purpose of the facade, in the first Ivy versions there were far less
options and features, and thus a single point of entry was nice. Now that
Ivy is providing a wide range of services, it is much easier to maintain
split into several services or engines. But is it easier to use directly
from the separate engines, or is the facade still interesting now that it
has been simplified (only a few methods per service, instead of numerous
ones with different parameters in previous version).

So I'm in favor of keeping the facade, but I'm open to argument against it.

Xavier

--
> Gilles SCOKART
>



-- 
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/