Bitten by the Decorator pattern…
I had an experience a few weeks ago where one of my favorite design patterns actually ended up costing me. This is all part of my explorations into the .NET
My current project is an Ajax enabled ASP.NET/C# app. It’s a completely lightweight stateless app (at least stateless from the perspective of the entire server tier, although quite a lot of state in maintained client side in Javascript). Given this approach, my data access is done through a lightweight layer of DAO objects which in turn use parameterized SQL to hydrate my domain objects. Sitting between my data layer and my Sybase RDBMS is a black box API to manage my connections to this store. Usage of this API is enforced by the corporate guidelines of my current client. When requesting a connection, this API gives you back your IDbConnections and IDbCommands, abstracting away from you the vendor specific implementation classes.
When writing my apps data layer I often like to log the SQL to a debug switch, all nile world isis sexfreepornvideos 100porno kid 3dpornography 1940 sporn allieamateur sex judyamatuer teen innocent jap moviessluts amateur teen Map


