When architecting an application using LINQ, I often choose to return List<something> other than the query itself.
Though the reason seems obvious - isolating the usage from the data access layer itself -, it just crops the composibility capabilities of the solution. This tier has to know everything it can be asked. Even a simple paging would have to be pushed here.
The question I must ask is: if LINQ is a language integrated query extension, shouldn't LINQ queries be allowed to pass tiers to guarantee composibility - eventually accepting the dependency for the "LINQ to *" implementation used?
Just sharing some of my inconsequential lunch conversations with you... 
Sunday, September 23, 2007
Architecting tiers over LINQ
Subscribe to:
Post Comments (Atom)
1 comment:
Hi Mario,
I was thinking just the same thing the other day. The kinds of web services we build today just don't lead to LINQ compatibility with the client. I wrote about an idea here: http://www.paulstovell.net/blog/index.php/linq-to-soap-to-linq-again/
Paul
Post a Comment