• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOModeler Conceptual Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModeler Conceptual Question


  • Subject: Re: EOModeler Conceptual Question
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 13 Jan 2004 13:50:20 -0800
  • Organization: Global Village Consulting, Inc.

james cicenia wrote:

If my portal screen instantiates a few sets of object arrays for session1 will
those objects be only quickly referenced by user2 is session2? Or will it
have to go out and retrieve those objects again? Is Web Objects smart
enough to know that they are the same set of objects and share them?


The data for the objects does not exist in the session, only references to the snapshots in the shared object store. So, in a sense, it will share them. As to whether it goes to the database again, that depends on whether you do a fetch or not, and on how old the data is. Fetches *always* go the db. Always. For other objects access the default is to reuse the data if it is less than an hour old. Of course, there all sorts of tweaks, hints, and overrides to control this. See FAQ links on www.wodev.com.


Finally, I am planning on using my lastModDate and lastModUserId as
the optimistic lock fields.
That seems redundant.

This would mean that I would want most
setMethods to also set the lastModeDate and lastModUserId.
That seems like inappropriate behaviour. Set methods should not have side effects. Yes, I'm a purist too. :-) See my postings yesterday on editing context / eo co-operation for a better way.


Would this make it easier for edits to the database
I don't understand.


and would it make it easier
for webobjects to know about changes to the "shared" objects?

EOF knowing about changes to shared objects is pretty much the whole point of EOF. That is EOF's main job: maintaining object graph consistency.

Chuck

--

Chuck Hill                                 email@hidden
Global Village Consulting Inc.             http://www.global-village.net

Progress is the mother of all problems.
- G. K. Chesterton
_______________________________________________
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.

References: 
 >EOModeler Conceptual Question (From: james cicenia <email@hidden>)

  • Prev by Date: Re: NullPointerException only after first call to batchFetchRelationship
  • Next by Date: Re: EOModeler Conceptual Question
  • Previous by thread: EOModeler Conceptual Question
  • Next by thread: Re: EOModeler Conceptual Question
  • Index(es):
    • Date
    • Thread