[ http://jira.magnolia.info/browse/MAGNOLIA-1667?page=all ]
Grégory Joseph resolved MAGNOLIA-1667.
--------------------------------------
Resolution: Fixed
David: yeah, we considered an ajax-based solution, but time constraints and the
fact that we wanted to stay as independent from anything as possible made us
stick to the simple solution.
I understand your pain with IE's tick, but otoh I wonder how you can live with
the same tick on every link you click then ;-) (please reassure, the same
setting to turn the beep-on-link-click off also turns the beep off when the
pages reload??)
> 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.5 RC1
>
>
> 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
----------------------------------------------------------------
