Alex Fernández <[EMAIL PROTECTED]> writes:
>
> In fact, if the component configuration cannot be integrated in our
> global configuration scheme, it will not do.
My concern as well.
> So, in a word, we don't need components that integrate with each other;
> we need components that need no integration at all. Perhaps we would be
> better off with a framework; but that's not what we think.
>
> I'm only talking about our particular needs (one small project within
> Telefonica I+D), but I feel it's not so uncommon.
I don't this is uncommon, I've been there alot of times myself. A framework
is good, but loose coupling and reusability of components are well worth
pursuing as well. The point is to design your components so they may
integrate with any framework and put the framework specific code in the
framework itself.
regards,
Gunnar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
