just approaching to Tuxedo and a n-tier application and I should define
the architecture as soon as possible. Now i am just trying to address a
potential problem stressed out by some developer: the client app will
cope with tons of basic data... from a data flow perspective it would be
nice to retrieve data just once (at application startup) storing data in a
'sort of' local cache. The question is how to sync data if someone change
them in the DB? (well known problem)
I thought of using Unsolicited Messages to send back "alteration" to the
client whenever a modification has been committed to an entity in the
database.
Now my questions are:
1) Is there any sort of "best practice" around that shows this or other
solution?
2) How UnsMsgs are reliable for this use?
3) Any other idea?
Thanks in advance,
/G