datareader over remoting infrastructure
-
Here's the scenario: 3 machines. Web server - running ASP.NET App server - running .NET assemblies db server - running SQL 2000 We are exposing .NET objects, via remoting, on the app server and allowing consumption by the web server. The team has been keen to pass datareaders (because "they're faster") from the business objects on the app server to the ASP.NET pages on the web server. My argument, as the architect, is: 1. datareaders maintain a connection to the database and that means that the ASP.NET layer needs to take on more responsibility. 2. datareaders over remoting. WTF? No, just no, don't argue. AGGHGH :mad: 3. datasets are more programmable (my opinion) 4. the real benefit of datareaders over dataset will become more apparent when dealing with large resultsets, which we're gonna avoid anyway. What does CP feel about datareaders over remoting? Cheers, Simon "Sign up for a chance to be among the first to experience the wrath of the gods.", Microsoft's home page (24/06/2002)