Thanks, Diego. My application is a server for medical imaging orders.
I have a farm of load-balanced servers connecting via NH to a SQL
Server db. Clients
connect to the server via WCF services. I am using memcached as my
distributed
cache.

To edit an order, a user chooses it from a special list.
When a user begins editing, the order is removed
from all other users lists. This is the application-level "lock"
I was mentioning.

So, it sounds like I can set an infinite timeout for my entity and
query cache.
Cached queries will still be invalidated when timestamps change after
table update.

  --Jorge


On Nov 13, 7:54 pm, Diego Mijelshon <[email protected]> wrote:
> 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.

Reply via email to