Re: Best Notification Framework
Re: Best Notification Framework
- Subject: Re: Best Notification Framework
- From: Dov Rosenberg <email@hidden>
- Date: Tue, 03 Feb 2004 12:31:42 -0500
Actually supporting multiple JMS servers didn't seem to be a big issue, the
differences between them seem to be the URL for getting the initial context
and specifying the connection factory and topic name. Those things are
already handled in the JMS change notification framework to a certain
extent.
We have had to spend some time refactoring some of the existing change
notification code to work within our environment.
One of the things that we discovered today was when the subscriber was
trying to process the changes, the update wouldn't happen on a consistent
basis depending on the load.
We commented out the line in the subscriber.processUpdates that records a
new snapshot in the EODatabase. The forgetsnapshot method basically
invalidates the object associated with the global id, manually overwriting
the snapshot with the info passed didn't seem to work on a consistent basis.
It seems to work if we let the framework update the snapshot itself.
--
Dov Rosenberg
Conviveon Corporation
http://www.conviveon.com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.