Re: ERRrest session defaultEditingContext
Re: ERRrest session defaultEditingContext
- Subject: Re: ERRrest session defaultEditingContext
- From: Samuel Pelletier <email@hidden>
- Date: Tue, 10 Dec 2013 14:22:39 -0500
As I have done the error many times in the past, are you sure about the 15 minutes? The delay is in ms not in seconds.
I now write those constant like this: EOEditingContext.setDefaultFetchTimestampLag (15*60*1000);
I do not see how using the session EOEditingContext would change anything except for this settings. I would try to create an EC and set it's fetchTimestamp to something in the past to see if this change the behaviour.
Samuel
Le 2013-12-10 à 09:20, Michael Kondratov <email@hidden> a écrit :
> 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