Are there ever any performance (speed & memory) benefits to using a properly-implemented singleton object vs. caching a single object and fetching it out of cache as it is needed?
We ve got a smart client that talks to a SQL Server database via WCF, displaying the entities in the database, and allowing the user to edit those entities. Some of the WCF calls return a large data ...