[jboss-dev-forums] [Design of JBossCache] - Re: SELECT FOR UPDATE semantics

[bstansberry@jboss.com]

"manik.surtani at jboss.com" wrote : Is the options api the best/cleanest way to do this?

Not sure about best.  It perturbs things the least.  The alternative I can think of would be to add a method to Cache.  But then all the interceptors that check for "get" calls would have to have that method(s) added.  And a target method would have to be added to CacheImpl.  With the Option, everyone is blissfully unaware except for PessimisticLockInterceptor.

anonymous wrote : Like you said, as it only applies to pessimistic locking, it does seem fairly straightforward to implement.

Yeah, I took a look at the interceptor yesterday to check for any gotcha, and it took me about 10 mins to add it w/ a simple 3-4 statement if block. Didn't test at all though.

anonymous wrote : Is there a JIRA task for this?

No, I wanted to check on the forum first whether people thought the whole concept was off. If you think its a useful feature, I'll open one.  Deciding exactly how to implement, timing, etc can come later.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998297#3998297

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998297