hi, i have an application where i need that calling session.Get(id) will always retun the same object istance.
as solution i want to use the same session for all the application life, there are few/none concurrency use of it so i think to wrap it in a threadsafe class that will use a lock for every method call.

do you think that i can have problem with this solution?

Do you want to leave a session open across multiple HTTP requests? When do you commit (the transaction is flushed and closed on commit)? Also, if there are any concurrent users things will get out of sync because everything will be eternally in your L1 cache.

You say you always need the same instance of an object (==). Can you write your own equals operator or just compare the key?