---------- Forwarded message ---------- From: Dimitris Zenios <[email protected]> Date: Tue, Jul 23, 2013 at 3:03 PM Subject: Re: Tapestry 5.4 Bug To: Howard Lewis Ship <[email protected]>
Hi Howard. Sorry for bugging you again about the amd problem.After investigation, it looks like there is no solution to this problem and unfortunately this bug also affects production mode.The only solution to the current problem is to have cache busting through url parameters in order not to pass through google chrome cache storage. On Tue, Jul 23, 2013 at 11:15 PM, Dimitris Zenios <[email protected] > wrote: > And this please > https://groups.google.com/forum/#!searchin/requirejs/chrome/requirejs/x5Z-eZMzKwI/gSccWU46CVAJ > > > On Tue, Jul 23, 2013 at 10:47 PM, Dimitris Zenios < > [email protected]> wrote: > >> Also have a look at this http://harrywolff.com/tag/require-js/ >> >> >> On Tue, Jul 23, 2013 at 10:43 PM, Dimitris Zenios < >> [email protected]> wrote: >> >>> You are right.I could not reproduce this problem with firefox. >>> >>> >>> On Tue, Jul 23, 2013 at 10:37 PM, Howard Lewis Ship <[email protected]>wrote: >>> >>>> Ultimately, I suspect this is a Chrome problem, not a RequireJS >>>> problem. Still, he may have some feedback. >>>> >>>> >>>> On Tue, Jul 23, 2013 at 12:33 PM, Dimitris Zenios < >>>> [email protected]> wrote: >>>> >>>>> Thanks for the reply. >>>>> >>>>> I haven't tested it on production yet.i will test it and let you know. >>>>> >>>>> Also i am not using geb.it happens very often when manual testing the >>>>> application. >>>>> >>>>> You can easily test it your self.create a pagelink that loads the page >>>>> you are inside and click it mores than 5 times very fast.or while the >>>>> response is loading.you will see it happen.javascript will start throwing >>>>> errors. >>>>> >>>>> Finally i haven't ask the author of require.js yet.i was hoping i can >>>>> find a solution before start asking >>>>> >>>>> >>>>> Sent from my Windows Phone >>>>> ------------------------------ >>>>> From: Howard Lewis Ship <[email protected]> >>>>> Sent: 23/7/2013 21:56 >>>>> To: Dimitris Zenios <[email protected]> >>>>> Cc: Tapestry development <[email protected]> >>>>> Subject: Re: Tapestry 5.4 Bug >>>>> >>>>> This is very problematic, as cache-busting is exactly the opposite of >>>>> everything else Tapestry's asset pipeline is doing. >>>>> >>>>> Is this something you see only in testing, or also in production? (or >>>>> integration testing?) >>>>> >>>>> If you are using Geb, one thing that might help is: >>>>> >>>>> waitFor { $("body").getAttribute("data-page-initialized") == >>>>> "true" } >>>>> >>>>> The data-page-initialized attribute is set after Tapestry has executed >>>>> all of the page inits, which can't happen until after all modules have >>>>> been >>>>> loaded. >>>>> >>>>> What does James Burke (RequireJS author) say about this? >>>>> >>>>> >>>>> >>>>> On Tue, Jul 23, 2013 at 11:22 AM, Dimitris Zenios < >>>>> [email protected]> wrote: >>>>> >>>>>> Ho howard please have a look at this bug.In my opinion its a 5.4 >>>>>> blocker bug. >>>>>> >>>>>> I have been using tapestry 5.4 since alpha 3.Its quite stable.The >>>>>> only problem i have found until now is that sometimes when refreshing >>>>>> pages >>>>>> to frequently javascript does not work with random errors of >>>>>> undefined.Even >>>>>> after page loads ok.It looks like that require.js is stopped while >>>>>> downloading a module through refresh and the next time it gets the >>>>>> corrupted js file instead of a freshly new.The only way to fix it is to >>>>>> clear the cache.Others reported this problem regarding require.js caching >>>>>> also and suggested to append a value to each of the script urls for cache >>>>>> busting. >>>>>> http://stackoverflow.com/questions/15803021/requirejs-caching >>>>>> >>>>>> http://stackoverflow.com/questions/8315088/prevent-requirejs-from-caching-required-scripts >>>>>> >>>>>> Best Regards >>>>>> Dimitris Zenios. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Howard M. Lewis Ship >>>>> >>>>> Creator of Apache Tapestry >>>>> >>>>> The source for Tapestry training, mentoring and support. Contact me to >>>>> learn how I can get you up and productive in Tapestry fast! >>>>> >>>>> (971) 678-5210 >>>>> http://howardlewisship.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Howard M. Lewis Ship >>>> >>>> Creator of Apache Tapestry >>>> >>>> The source for Tapestry training, mentoring and support. Contact me to >>>> learn how I can get you up and productive in Tapestry fast! >>>> >>>> (971) 678-5210 >>>> http://howardlewisship.com >>>> >>> >>> >> > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
