Re: Caching reference data
Re: Caching reference data
- Subject: Re: Caching reference data
- From: Ben Ketteridge <email@hidden>
- Date: Sun, 17 Oct 2004 19:18:08 +0100
It occurs to me that you could solve this by storing the user id of
the user in the reference data and implementing a very simple getter
(caching in private instance variables if you like) to simulate the
relationship - then you can put your reference data in the EOSharedEC
and the users remain in the EOECs.
Not difficult, and not exactly the WO-Way... but it should work :)
Ben Ketteridge
On Sun, 17 Oct 2004 11:13:36 -0700 (PDT), Jason McInnes
<email@hidden> wrote:
> You're right that the data isn't truly static -
> although it will change very, very rarely.
>
> Unfortunatley, even if I had a separate application to
> manage the reference data, I'd still have the same
> problem because the reference entities still point to
> a dynamic entity, namely, the user entity.
>
> I'm pretty sure I'll have to implement my own caching
> scheme because of my model. Sigh. If anyone has any
> suggestions or gotchas, I'd love to hear them.
>
> Jason
>
>
>
> --- Ben Ketteridge <email@hidden> wrote:
>
> > On Sun, 17 Oct 2004 09:57:56 -0700 (PDT), Jason
> > McInnes
> > <email@hidden> wrote:
> > > I want the benefit of caching these reference
> > types
> > > without the overhead of having to do the
> > > localInstanceOfObject step storing them in arrays
> > on
> > > my Application object, and I'd like to not have to
> > > change my model (e.g., storing just the user name
> > on
> > > reference types rather than a relationship to
> > user).
> > > Am I out of luck?
> > Yes, basically.
> >
> > If you want the power of WORelationships that change
> > every time the
> > object changes, then, clearly, the object is not
> > truly static.
> > Therefore, it does not belong in the
> > EOSharedEditingContext. Such a
> > Context is for 'true' static data that never*
> > changes.
> >
> > *Well, almost always never... you can use
> > localInstanceOfObject on the
> > rare occassion that the reference data changes, but
> > the existing
> > shared instances may well not get the updates
> > without being refreshed.
> >
> > Hmmm, sounds to me like a case for a maintenance
> > program to maintain
> > 'reference data' outside the main program.
> >
> > $0.02,
> > Ben Ketteridge
> >
> > ps. caveat - I've not used EOSharedEditingContexts
> > for a few years,
> > though maybe I ought to reconsider adding such
> > optimisations to our
> > static data.
> >
> > --
> > | Ben Ketteridge email@hidden, aka
> > Gremlin |
> > | It is by caffeine alone that I set my mind in
> > motion. |
> > | It is by the coffee that the thoughts acquire
> > speed, |
> > | the lips acquire stains, the stains become a
> > warning. |
> > | It is by caffeine alone that I set my mind in
> > motion. |
> >
>
> =====
> Jason McInnes
> 2 Degrees
> Cell: 206.849.3680
> Email: email@hidden
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
_______________________________________________
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