John,

>Basically he is trying to prevent having the same business logic in several areas. In a 3 tier design, developers have most business logic in the “business object layer” but will typically also include logic in the UI (or even the data access layer) for “better” user experience. <

Well, yes, I agree with that (preventing having the same biz logic in several places). I don't know if I agree with doing away with DataSets to accomplish this though. But then, I haven't read the book, so what do I know? <g> Seriously though, it sounds like it might be interesting reading. Maybe I should pick it up one of these days.

Thanks for the reply!
~~Bonnie


>>> Anyway, just curious ... can you summarize some of his objections?
>
>Basically he is trying to prevent having the same business logic in several areas. In a 3 tier design, developers have most business logic in the “business object layer” but will typically also include logic in the UI (or even the data access layer) for “better” user experience. His approach is to move all business logic into the biz object and serialize it back and forth (the DAL becomes an app server that just calls-back the biz object). This is where it differs from the “normal” 3-tier model. You can serialize datasets (which are very fat) but you still have business logic elsewhere – not good design. I believe his code, using a DataReader, is even faster that a DataAdpater with a typed dataset (but I have not tested it). There is a LOT of other issues, such as Security Principal the biz layer and DAL are running on.
>
>The first chapter or two really goes into the reasons and I recommend the book for at least it. You really should read the book. In fact this is the first Apress book I would recommend (many bad experiences(.
>
>I disagree with some of his approaches -- mainly with design patterns and would like to see more component based (i.e., using interfaces). I would like to combine this approach with Martin Fowler’s enterprise patterns. I still new to patterns.
>
>John