Does .NET architecture allow to implement a solution where a Web Service exposes an ADO.Connection object so that an ASP.NET client could retrieve such object, open its local ADO.Recordset on it, and use it at its own discretion as thou the ADO.Connection object was created on the clients PC?

If yes, how to implement exposing an ADO.Connection object from a Web Service, and a clients requesting to get that object?

If No, what should be the closest architectural solution?