Pretty much. What kind of application is it? (desktop, web, ...)
Anyway, the only way for a cache entry to be stale is to have the data
modified by a different process (or different instance of the same process
running in a different machine, of course) while using a non-distributed
cache.
Diego
On Sat, Nov 13, 2010 at 20:11, Jorge <[email protected]> wrote:
> Hello!
>
> Sorry for my continuing cache questions, but I really need to figure
> this out:
> In my environment, my NH client is the only app to touch the database.
> Also, there are never any concurrent writes; there is an application-
> level lock
> preventing this from happening. So, can I assume that an entity in the
> entity
> cache will never become stale?
>
> Thank you!
> Jorge
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
