Server to non ejb client pattern ?
Hi,
Are there any patterns covering publishing updates to non ejb clients ?
I assume I'm dealing with a very common scenario, specifically object definitions being updated in a central location and used by multiple remote clients. My non ejb clients will have local caches of their data so I want a mechanism to notify them of changes.
I'm looking at publishing notifications which will be consumed by MDB's and they in turn call Session beans to notify clients. This will involve maintaining references (somewhere) to currently active clients and using some callback API.
The alternative is have the client caches perform version checking with the server side according to some policy (ever time its accessed, periodically, etc)
Any comments appreciated
Cheers,
mairt
