[ http://jira.magnolia.info/browse/MAGNOLIA-1221?page=comments#action_12836 ] Philipp Bracher commented on MAGNOLIA-1221: -------------------------------------------
The original intention of spliting the requests was the saving of memory. The ordering problem is not solved be making bulk activation requests in my opinion, because one can also manually acitvate single pages in different orders. But sure solving transactional behavior will be more difficult by sending multiple requests. > Tree activation should be in one transaction instead of separate http calls > --------------------------------------------------------------------------- > > Key: MAGNOLIA-1221 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1221 > Project: Magnolia > Issue Type: Task > Components: activation > Affects Versions: 3.0 Final > Reporter: Sameer Charles > Assigned To: Sameer Charles > Fix For: 3.0.x > > > Maintain user transaction on subscriber while receiving content. > Currently on tree activation authoring instance sends multiple unrelated > activation requests to subscribers which kills the cache after every > successful > request and can also result in strange ordering if content is received from > multiple sources -- 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://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
