Basic question about modification to existing entry / dirty flag

[jugglingcats]

In our use case, we'll be retrieving objects from the cache and putting them through a pipeline process. The object graph for each entry is moderately complex, and the entry may be modified at various points in the pipeline.

I'm assuming (for a distributed / store backed cache) that modified objects have to be "re-supplied" to the cache after modification. That's my first question.

Does anyone have a recommended pattern for achieving this in practice? I'm a bit loath to implement 'isDirty' semantics in my object(s).

Thanks, Alfie.

[wdfink]

If you use a remote access to the case the object which you retrieve is a new object, so yes you need to push it back after change it.

It depends on your requirements what approach you might use.

You should describe a bit more what your environment look like and what you try to achieve.

[sannegrinovero]

You could use Hibernate OGM to have it track dirtyness as you would do with any JPA provider, but it currently works only with embedded cache (no Hot Rod yet).

Also, you could consider to simply re-write the whole graph back into the grid: being a very fast operation it shouldn't be a problem (YMMV)