>That may or may not be a good idea. The cost of constructing XML from the query results may be higher than just passing the ADO. I have not had any problems passing ADO around my n-tier applications.
>
Even across different servers? I've not benchmarked, but I always thought that was a no-no given the fact that you'd be pointing to an object on a different server.....
>
>>
>>To be honest, I'd recommend against passing the ADO objects -- consider passing XML instead. Then, pass XML back to the business object after the user has entered data, construct your INSERT or DELETE or UPDATE statements in the business layer, and send to the database (probably via ADO calls).
>>
>>The reason I'd recommend against passing objects is that the overhead is much heavier especially if you have the presentation and business objects on different servers (likely, in a web environment).
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. - Bertrand Russell
