Re: Multiple Servers and Shared Editing Contexts
Re: Multiple Servers and Shared Editing Contexts
- Subject: Re: Multiple Servers and Shared Editing Contexts
- From: Karl <email@hidden>
- Date: Tue, 18 Nov 2003 10:40:58 -0500
Did you ever try using one of the notification frameworks? I am
playing with the Wonder JMS-based framework but can't seem to get it
working just yet.
I would like to propagate updates individual rather than having to
reload all of the data. The number of updates is small compared with
the total amount of data.
Karl
On Nov 18, 2003, at 10:24 AM, Geoff Hopson wrote:
Yep - I did something similar on the Fortnum & Mason site. I cache the
product catalog across multiple instances across multiple hosts in
EOSharedEditingContexts, and have an admin app to manage the product
catalog and content management. When the admin person hs made changes
and is ready, he hits a button to "reload the instances". The way this
works is the admin app has a WOLongResponsePage that sends a direct
action to each instances (I know I have between 5 and 20) using a
WOHTTPConnection, waiting for the response. The direct action is
implemented in the main shopping application, and when the instance
receives the request, it refreshes the EOSharedEditingContext holding
the product catalog and the content.
Not at liberty to share code, I'm afraid...
Geoff
On Tuesday, November 18, 2003, at 02:52PM, Karl <email@hidden>
wrote:
Hi List,
Has anyone had any experience with multiple instances of WO when you
are using the shared editing context?
We are keeping a lot of lookup tables in the sharedEC for performance
reasons and go through the process of taking a local copy, updating in
a privateEC, etc, when we need to update a value.
This all works just fine when you have just one instance of the app
running. The sharedEC observes the change in the privateEC and simply
updates itself (we specifically fetch any inserts that we make into
the
privateEC).
Has anyone had any experience of running multiple instances and had to
deal with the fact that the sharedEC doesn't notice changes made by
other instances?
It looks like we have to implement our own notification framework to
keep the sharedECs in sync across multiple instances on multiple
servers.
Let me know if I am missing something....
Karl
_______________________________________________
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.
_______________________________________________
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.