>
>Just one point on this: I would be glad to get an ILayer because this would solve a few diffculties we have too. But one thing I fell over discussing with Armin is that when you get 1 i-Layer you would probably need two. (One for Company base stuff and one for Application specific stufff) or three or four..... Armins hook-concept seems to be quite more flexible, even if it is a bit complicated :-)) But we all love complicated stuff :-)
>
>Marcus

I'd setting for one I-Layer right now ;-) I like the approach of hooks & behaviors better than adding more layers. I've found it's way too easy (for me) to screw things up on multiple projects when I've got a lot of layers. Hooks can address the same sorts of problems, but they can be applied locally, and then reused in other apps when you're ready for them.