Essentially, everything is stored in a modelglue scope which is located in the application scope.
So whenever the parameters exist, we just reload the entire modelglue framework based application, which flushes everything. If you are interested in the mechanics, do a find for the string reloadKey in the ModelGlue framework. DW On Mon, Oct 19, 2009 at 7:59 PM, Drew Wells <[email protected]> wrote: > Actually I was asking where init=true is triggering the refresh, is this a > MG or Coldspring thing. I'm curious how this is used to remove all the > caching. I didn't know this trick before and had to remove the application > variable to refresh my cache. > > On Mon, Oct 19, 2009 at 3:22 PM, Dan Wilson <[email protected]> wrote: > >> What do you mean? >> >> If the application is reloading on each request (reload=true) then you >> don't need the url parameter. >> >> if the application is NOT reloading on each request (reload=false) then >> you MUST use the url parameter to reload, even when you just change the XML >> value from true to false. This is because MG does everything it can to be as >> fast as possible, including not even looking at the ColdSpring.xml file once >> a reload has happened. >> >> DW >> >> On Mon, Oct 19, 2009 at 3:14 PM, Drew <[email protected]> wrote: >> >>> >>> Definitely a good tip, init=true seems to work well. Is init=true >>> built into MG/Coldspring? Toggling the reload value in the >>> ModelGlue.xml does nothing after you have turned reload off. >>> >>> On Oct 16, 1:31 pm, Jared Rypka-Hauer <[email protected]> wrote: >>> > Just set up a tab with ?init=true on the URL (or whatever you changed >>> > the reload url variable and value to if you did that) and refresh when >>> >>> > you change a controller or model object. That way you can develop, >>> > incorporate your changes and have the speed you need for building your >>> >>> > views. Note that the only changes that need a refresh like that are to >>> >>> > the XML (MG or ColdSpring, controller code and/or any model code that >>> > gets stuck in a persistent scope. >>> > >>> > Yeah, it still requires you to refresh from time to time (and a lot >>> > depending on what you're working on), but it's better than 11 seconds >>> > for every request regardless. >>> > >>> > Incidentally, until CF9, this was SOP for a lot of us developing large >>> >>> > MG projects. >>> > >>> > J >>> > >>> > On Oct 16, 2009, at 12:25 PM 10/16/09, Drew wrote: >>> > >>> > >>> > >>> > >>> > >>> > > Report Execution Times is off, I have only minimal access to server >>> > > settings so I can't turn off the memory tracker. Something tells me >>> > > that isn't going to give me an order of magnitude in speed like I >>> > > should be seeing. Turning off reload/debug made the page instant, of >>> > > course I can't develop now since it wont detect many changes. >>> >>> >> >> >> -- >> “Come to the edge, he said. They said: We are afraid. Come to the edge, he >> said. They came. He pushed them and they flew.” >> >> Guillaume Apollinaire quotes >> >> >> > > > > -- “Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew.” Guillaume Apollinaire quotes --~--~---------~--~----~------------~-------~--~----~ Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en -~----------~----~----~----~------~----~------~--~---
