• 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: ERRrest session defaultEditingContext
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERRrest session defaultEditingContext


  • Subject: Re: ERRrest session defaultEditingContext
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 10 Dec 2013 16:27:34 +0000
  • Thread-topic: ERRrest session defaultEditingContext

IIRC, they create a new EC per request so when the request ends there are no references to the EOs so they get garbage collected.  I am surprised using the session's default changes this as it should not be retaining references to its objects (unless you have enabled that).   

You can also look at the ERXEnterpriseObject cache if you only want to prevent some of the objects from being refetched.

Chuck



-- 
Chuck Hill             
Executive Managing Partner, VP Development and Technical Services

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

Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C! 

Global Village Consulting ranks 44th in 25th annual PROFIT 500 ranking of Canada’s Fastest-Growing Companies by PROFIT Magazine!

On 2013-12-10 6:20 AM, "Michael Kondratov" wrote:

Time lag is 15 minutes. Rest routes seem to always fetch data from the database unless I manually fault objects into session's editing context. It's a huge performance hit.

Sent from my iPad

On Dec 10, 2013, at 8:34, Samuel Pelletier <email@hidden> wrote:
Hi,
The snapshot cache is under EOEditingContext. Check your EOEditingContext.defaultFetchTimestampLag(), if is it very low, you are asking for refreshed objects when you fetch.
Samuel
Le 2013-12-09 à 13:09, Michael Kondratov <email@hidden> a écrit :
Is there an easy way to get ERRest to use session’s default editing context if session is available? It seems I am missing out on WebObject’s snapshot caching when not using long lived editing contexts.
Michael Kondratov
Aspire Auctions _______________________________________________
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

References: 
 >Re: ERRrest session defaultEditingContext (From: Samuel Pelletier <email@hidden>)
 >Re: ERRrest session defaultEditingContext (From: Michael Kondratov <email@hidden>)

  • Prev by Date: Re: Qualifier against target entity?
  • Next by Date: Re: Qualifier against target entity?
  • Previous by thread: Re: ERRrest session defaultEditingContext
  • Next by thread: Re: ERRrest session defaultEditingContext
  • Index(es):
    • Date
    • Thread