Changes between Initial Version and Version 1 of Ticket #16684, comment 7


Ignore:
Timestamp:
Feb 8, 2013, 12:07:38 AM (7 years ago)
Author:
Patrick Ruzand
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16684, comment 7

    initial v1  
    1 Because this use case where thousands of shapes are created and destroyed during the app lifecycle is quite specific and due to IE bad memory management, a possible patch would be to recycle the ids of the destroyed shapes. This way, it would limit the number of intern strings  the browser has to handle. \\
    2 But since recycling ids makes an id not "unique" anymore, and therefore may have some possible impacts on existing application, the patch would need to be enabled via a dojoConfig flag.
     1A possible patch would be to recycle the ids of the destroyed shapes. This way, it would limit the number of intern strings  the browser has to handle. \\
     2But since recycling ids makes an id not "unique" anymore, and therefore may have some possible impacts on existing application, and because this use case where thousands of shapes are created and destroyed during the app lifecycle is quite specific and due to IE bad memory management, the patch would need to be enabled via a dojoConfig flag.
    33
    44I attach such patch to the ticket. The idea is:
     
    66* when disabled, the existing behavior is kept.
    77* when enabled, the id of a destroyed shape is stored in a cache, and when a new shape is registered, the cache is checked for available ids.
    8