Comments on: Ruby on Rails Watch out here comes Blinq http://wagnerblog.com/2006/06/ruby-on-rails-watch-out-here-comes-blinq/ Development Ideas and Ramblings Tue, 14 Oct 2008 20:14:10 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Thomas Wagner http://wagnerblog.com/2006/06/ruby-on-rails-watch-out-here-comes-blinq/comment-page-1/#comment-315 Thomas Wagner Thu, 29 Jun 2006 01:26:59 +0000 http://wagnerblog.com/?p=635#comment-315 Thanks for the comment Polita. Truth be told, I am trying to make sense of the new directions of ADO.NET and I am still not sure where it fits. Maybe if some of the ORM guys in the community post comparative analysis I may get a better understanding. At the moment my framework called NGPF utilizes a domain object approach so its a tad removed from all that new fancy stuff you guys are coming up with :) Thanks for the comment Polita. Truth be told, I am trying to make sense of the new directions of ADO.NET and I am still not sure where it fits. Maybe if some of the ORM guys in the community post comparative analysis I may get a better understanding. At the moment my framework called NGPF utilizes a domain object approach so its a tad removed from all that new fancy stuff you guys are coming up with :)

]]> By: Polita http://wagnerblog.com/2006/06/ruby-on-rails-watch-out-here-comes-blinq/comment-page-1/#comment-314 Polita Wed, 28 Jun 2006 21:56:45 +0000 http://wagnerblog.com/?p=635#comment-314 Thomas, thanks for the great review! I agree that we have some work to do (with both LINQ in general and the Blinq web form generation tool) to work out the right way to promote an n-tier data design. In the current previews of LINQ, the best answer to promote encapsulation and limit unwanted access to data from upper tiers is to call ToList() on the IEnumerable<t> returned by LINQ calls, which works but isn't that elegant and may have performance implications. Both my team (the ASP.NET team) and the LINQ teams are working on finding the right solution for that problem. Worry not; we still believe in the n-tier model. :) Blinq itself is meant as a prototype for the VS-integrated web page generator we are planning for the next version of Visual Studio. With better integration, you can imagine many more improvements to what Blinq does today. It's great to get feedback like yours so we know what's most important to our customers before we ship. -P</t> Thomas, thanks for the great review!

I agree that we have some work to do (with both LINQ in general and the Blinq web form generation tool) to work out the right way to promote an n-tier data design. In the current previews of LINQ, the best answer to promote encapsulation and limit unwanted access to data from upper tiers is to call ToList() on the IEnumerable returned by LINQ calls, which works but isn’t that elegant and may have performance implications. Both my team (the ASP.NET team) and the LINQ teams are working on finding the right solution for that problem. Worry not; we still believe in the n-tier model. :)

Blinq itself is meant as a prototype for the VS-integrated web page generator we are planning for the next version of Visual Studio. With better integration, you can imagine many more improvements to what Blinq does today. It’s great to get feedback like yours so we know what’s most important to our customers before we ship.

-P

]]>