I think I've come to a crossroads where I am thoroughly misunderstanding something. I would like to be able to cache an object in its current state into the .NET cache. I realize this presents some complications due to disposal, and I can't really make heads or tails of the documentation regardings DirectStateAccesor and DisconnectedState operations. Is there a simple / straightforward way, using 4.5 RC2, to disconnect an object from the session and implant it into the .NET cache?

Sorry if this is a little vague and if there's anything else I can provide, I'd be more than happy to, I'm just not entirely sure what I would be able to supply for sample code that isn't beyond just the straight basics of this operation.

asked Apr 04 '12 at 13:30

GigMastersTech's gravatar image


One Answer:

Hello GigMastersTech,

The L2 Cache feature is only planned for the implementation, so for now the only way to cache some data from DataObjects.Net is to convert it to a POCO object and store it in cache of any kind.

The L2 Cache is planned for 4.7, see Roadmap.

answered Apr 05 '12 at 06:55

Dmitri%20Maximov's gravatar image

Dmitri Maximov

Got it. Thanks.

(Apr 05 '12 at 14:47) GigMastersTech GigMastersTech's gravatar image
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA