>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.

TIA

>
>>Ok, this sound nice (and familiar to me) but who/where does what 'he should not care about' ?
>>(because that is almost all I care about! )
>>
>>According to terminology I would suspect that this is happening somewhere in datalayer
>>or this is as well done at entity level ? (in som foundation classes of NET framework)
>>
>>What are the possibilities there in terms of programming / modelling / datamunging.
>>For instance I want to control contingency scenarios. (Multiple users accesing the same records etc)
>>
>>Pls don't tell me that this is blackboxed somewhere and customisable as easy as BIOS... {g}