• 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: EOF related objects present a lot in the heap
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOF related objects present a lot in the heap


  • Subject: Re: EOF related objects present a lot in the heap
  • From: Joseph Pachod <email@hidden>
  • Date: Fri, 26 Apr 2013 23:55:26 +0200

Thanks a lot all for your answers. I'm new to the application I'm working, as well as EOF/WebObjects/Wonder, so excuse my naive questions and maybe incomplete answers. 

To put a bit of context, the application is a quite large one, spanning for more than a decade and quite some developers. So while I'm not afraid of changing stuff, anything which can't be done easily at a large scale is bound to be impossible to do (since being too much work if it cannot be automated in some ways).

@Chuck Hill
Regarding your suggestion, I haven't seen the talk in question (I looked for them, found 4, none speaking of this technique as far as I got it). Yet I'll check this option with our architecte in chief, because I'm unsure about the lifecycle of our pages (I would they they're created once and then reused if the same page is entered different times, so just the ec creation would be needed at different places. On the other hand, success/Cancel would be trivial to deal with).

removeAllActions() is already properly called.

On a more general level, I don't really get how the snapshot cache cleans itself up. My current understanding is that it keeps a snapshots of everything it put an hand on. These snapshots are then released only when the editing context is disposed (or garbage collected). Is this right ? Is there really no way to clear a bit this cache in between ?

@Henrique
We rely on validation, so we would prefer to keep it.

@Ramsey:
I've used wicket in my previous life, so going for such mechanism really rings a bell here. I'm currently looking for low hanging fruits before digging deeply into it: it's for sure on the radar. A pity though it wasn't used in production yet... Furthermore, we deploy on our customers servers: we can't easily tweak the db. Was the ERPersistentSessionStorage thought for different persistence mechanisms (file store, memcached) ? 

Thanks again you all :)

 _______________________________________________
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

  • Follow-Ups:
    • Re: EOF related objects present a lot in the heap
      • From: Ramsey Gurley <email@hidden>
    • Re: EOF related objects present a lot in the heap
      • From: Chuck Hill <email@hidden>
References: 
 >EOF related objects present a lot in the heap (From: Joseph Pachod <email@hidden>)
 >Re: EOF related objects present a lot in the heap (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: EOF related objects present a lot in the heap
  • Next by Date: Rule Modeler & Spinning Beach Ball
  • Previous by thread: Re: EOF related objects present a lot in the heap
  • Next by thread: Re: EOF related objects present a lot in the heap
  • Index(es):
    • Date
    • Thread