>>>Data layer should handle that. But, where that data comes from should be of no relevance to anything outside of the datalayer. Read up on Domain Driven Design. http://www.infoq.com/minibooks/domain-driven-design-quickly
>>
>>I just did (and nearly fell asleep).
>>
>>I asked about plumbings in the basement while you'v sent me to the roof (complex systems architecture). {g}
>>Now expressed in 'ubiqutous language' of a e-book you adviced, and relating to the 'domain' of my question,
>>Is there anything in the NET blogsphere or MS resources that sheds some light on basics/mechanics/best practices in pouring records
>>in/out of those 'repositories'. How do you create stream of 'entity' or 'aggregate' particles (records) and shoot them right
>>into the middle of 'repository' ? :)
>>
>>Or in simple foxpro terms, is there any resource out there that explains what it takes to to create something like simple
>>cursor adapter for instance. What are the prospects of building deacent custom backend handling tier in NET.
>>
>
>I'm not sure what exactly you are asking for so I apologize if I misunderstood. Very basic example of simple 3-layer ntier design using entities:
>
>http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=4531&lngWId=10
>
>Overview:
>
>http://www.exforsys.com/tutorials/csharp/building-web-based-n-tier-applications-using-csharp.html
>
>(I haven't looked at those in a couple of years - been using many layers since, but if I remember it was a nice simple design for getting the feel of layers in .net)

Saved the links
Thks+++ Tracy :)