On Dec 15, 2005, at 2:49 PM, Jesus Cea wrote:

>
> I would suggest to add a single line "connection.abort()" just
> below the
> "try", before any aplication logic. This line would check the
> connection
> and validate the cache before any heavy aplication code.
>
> Is this approach legitime?. Valuable?.

Yes.  You can either abort() or not as a request/transaction starts.
If you don't, you have a higher risk of finding out later that you are
holding an object that has changed.  The advantage is that you
avoid an extra round-trip message to the storage server.
Either way, you are making a bet on whether or not your cache
is currently up-to-date.

Some situations may make the pre-emptive abort() call more
attractive, but I'm not sure exactly how you would characterize
those situations.