[ http://jira.magnolia.info/browse/MAGNOLIA-1667?page=comments#action_14986 ] David Smith commented on MAGNOLIA-1667: ---------------------------------------
I loaded up a fresh copy this morning -- 88 tasks. I like the update page as opposed to the wait and pray method of initializing 3.0.x and previous -- very nice. It actually threw me a little -- I thought something was wrong when I saw only a 5k debug log after deployment. You're right -- it seemed like the vast majority of tasks went quickly with only a few long running tasks (typically bootstrapping). I'll build again tomorrow morning and see how the 3 second thing works if you have it committed in SVN. > Updatemech : the whole process should be running in a separate thread > --------------------------------------------------------------------- > > Key: MAGNOLIA-1667 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1667 > Project: Magnolia > Issue Type: Improvement > Components: updatemechanism > Reporter: Grégory Joseph > Assigned To: Grégory Joseph > Fix For: 3.1 > > > Threading: the whole process should happen in a separate thread rather than > during the request. This would help avoiding time outs and conflicts. (any > access to the page, once the process is started, would just display the > current state, i.e the list of tasks which have been executed, for instance) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
