Re: linking editing contexts from two apps
Re: linking editing contexts from two apps
- Subject: Re: linking editing contexts from two apps
- From: Chuck Hill <email@hidden>
- Date: Wed, 05 Sep 2012 09:50:22 -0700
On 2012-09-05, at 8:37 AM, Matteo Centro wrote:
> I've used ERJGroupsSynchronizer with success and I'm very happy with it. But, what if the app that updates my database is not a WO application, but something done directly on the db? What's the common practice?
I don't know if there is a common practice, a lot depends on your exact situation. You could poll the database for updates periodically. Or manage object freshness so that you get updated objects when needed.
> I think we should write an article for the Wiki about best practices on data freshness... I'm more than willing to start it
Mark Ritchie did a very good presentation on this at some WOWODC. And I have included some information in some of my presentations. I think... Those would be a good start to a write-up if there is not one already.
Chuck
> On Mon, Aug 6, 2012 at 2:56 PM, Theodore Petrosky <email@hidden> wrote:
> So I viewed Mike's presentation for ERJGroupsSynchronizer.
>
> wow, it just worked right out of the gate.
>
> So now I need to decide if I should set a timer to automatically fire a method to update the AjaxUpdateContainer on the company internal app.
>
> I am thinking I will warn the internal people to check their email for change notifications before altering rows. It's not a great solution, but it will work in a pinch.
>
> Ted
>
>
>
>
> --- On Wed, 8/1/12, Ted Archibald <email@hidden> wrote:
>
> > From: Ted Archibald <email@hidden>
> > Subject: Re: linking editing contexts from two apps
> > To: "Theodore Petrosky" <email@hidden>
> > Cc: email@hidden
> > Date: Wednesday, August 1, 2012, 6:17 AM
> > ERJGroupsSynchronizer might be what
> > you're looking for, Mike describes it in the video
> > "Project Wonder in Depth (WOWODC West 2009)"
> >
> > On Tue, Jul 31, 2012 at
> > 8:48 AM, Theodore Petrosky <email@hidden>
> > wrote:
> >
> > I
> > have a Wonder app that I did a while ago. This is an
> > internal app that is used in production.
> >
> >
> >
> > I have been asked to create a client facing version. Not all
> > fields will be editable and it will fire an email if they
> > touch anything.
> >
> >
> >
> > How do I maintain freshness of data? If my internal app
> > updates the data, how do I notify the client app. Or should
> > I not care and just make sure that the client app is always
> > going to the database?
> >
> >
> >
> > likewise if the client updates a row, how will my internal
> > app know?
> >
> >
> >
> > There are approximately 10000 rows of data (small) and it
> > only grows a thousand a year.
> >
> >
> >
> > Ted
> >
> > _______________________________________________
> >
> > 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
> >
> >
> >
> >
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/gvc/practical_webobjects
_______________________________________________
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