You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2006/08/31 11:31:22 UTC

[jira] Created: (JCR-552) Move listeners from item state to item state managers

Move listeners from item state to item state managers
-----------------------------------------------------

                 Key: JCR-552
                 URL: http://issues.apache.org/jira/browse/JCR-552
             Project: Jackrabbit
          Issue Type: Improvement
          Components: core
    Affects Versions: 1.1
            Reporter: Dominique Pfister
         Assigned To: Dominique Pfister
            Priority: Minor
             Fix For: 1.1


Clients interested in item state modifications directly subscribe to the item states, which is a very flexible approach. On the other side, it increases the memory consumption of an item state, because every item state holds a collection of its listeners. It further increases complexity, because item state listeners can potentially have a shorter life and might be garbage collected.

Listeners should therefore be moved to their associated item state manager. At the same time, this enables an item state manager to completely remove an item state from its cache and resurrect it at a later time without losing the listeners interested in notifications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (JCR-552) Move listeners from item state to item state managers

Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-552?page=all ]

Dominique Pfister resolved JCR-552.
-----------------------------------

    Resolution: Fixed

fixed in revision 438851.

> Move listeners from item state to item state managers
> -----------------------------------------------------
>
>                 Key: JCR-552
>                 URL: http://issues.apache.org/jira/browse/JCR-552
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.1
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>            Priority: Minor
>             Fix For: 1.1
>
>
> Clients interested in item state modifications directly subscribe to the item states, which is a very flexible approach. On the other side, it increases the memory consumption of an item state, because every item state holds a collection of its listeners. It further increases complexity, because item state listeners can potentially have a shorter life and might be garbage collected.
> Listeners should therefore be moved to their associated item state manager. At the same time, this enables an item state manager to completely remove an item state from its cache and resurrect it at a later time without losing the listeners interested in notifications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (JCR-552) Move listeners from item state to item state managers

Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-552?page=all ]

Dominique Pfister closed JCR-552.
---------------------------------


> Move listeners from item state to item state managers
> -----------------------------------------------------
>
>                 Key: JCR-552
>                 URL: http://issues.apache.org/jira/browse/JCR-552
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.1
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>            Priority: Minor
>             Fix For: 1.1
>
>
> Clients interested in item state modifications directly subscribe to the item states, which is a very flexible approach. On the other side, it increases the memory consumption of an item state, because every item state holds a collection of its listeners. It further increases complexity, because item state listeners can potentially have a shorter life and might be garbage collected.
> Listeners should therefore be moved to their associated item state manager. At the same time, this enables an item state manager to completely remove an item state from its cache and resurrect it at a later time without losing the listeners interested in notifications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira