Re: ERChangeNotificationJMS
Re: ERChangeNotificationJMS
- Subject: Re: ERChangeNotificationJMS
- From: Guido Neitzer <email@hidden>
- Date: Tue, 23 Oct 2007 09:38:47 -0600
On 23.10.2007, at 09:20, Gino Pacitti wrote:
Can I use the ERChangeNotificationJMS to synchronize instances from
2 apps?
Yes, you can if they share entities (models). Only be aware that if
you use OpenJMS as the service, you might see lockups. I've used
ERChangeNotificationJMS a while ago and it always locked up under
heavy load.
A temporary solution was to only broadcast global ids and invalidate
them on the receiving end. But still under really heavy load it
locked up inside OpenJMS. And when I see the slow, not to say
crawling, development of OpenJMS I'd use one of the other
synchronization methods (there are others in Wonder, like the
multicast synchronizer).
They both share the same database and I need updates/changes made
in the admin app to be visible in searched EOs (possibly already in
the cache) on the public view
Invalidate the caches earlier and let the database do the caching. Or
use raw rows. Or set relevant fetch specs to refresh their content if
you need that. Synchronizing might sound tempting, I found that it
adds more problems than it solves in all the cases where I used it.
But I didn't use one of the more modern solutions in Wonder.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden