nhibernate - Key Question on Custom ICache Implementation -

We have our own caching framework that works well and we like it. We want to wire it to NHibernate rather than take one of the other caching implementations for the NH.

I have written the implementation of NHibernate.Cache.ICache which pulls our structure along the National Highway. I base my implementation almost entirely on the basis of:

One thing that has gone out of the bat right now is that the Icache interface has a cache key type of objects, our framework I have noticed that using the strings is that the implementation of the upward side does the toasting on the key object (for example) which moves to the object and keeps (the object's) way.

My question:

The "key" object type in my test is string and it is the unit name.

My question:

>

is calling indiscriminately. Key example is toastring () a safe way (I am checking blank)?

If this implementation is really safe, then does it mean always a string?

If this is always a string, then why is this type of object?

NH people are more skilled than me, so this kind of thing I think is there something I'm missing here

appreciate any guidance - Cheers

class = "post-text" itemprop = "text">

The response has not been received, nor on the NH user group thread [1] I have concluded that calling key String () is safe in our custom implementation, but I am unhappy that I did not find any official guidance on this: (

See more details for the user group thread.

Cheers

[1]