DO NOT REPLY [Bug 33038] New: - ObjectNode's vector of children is never updated...

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33038>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33038

           Summary: ObjectNode's vector of children is never updated...
           Product: Slide
           Version: 2.1
          Platform: Macintosh
        OS/Version: Mac OS X 10.0
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: slide-dev@jakarta.apache.org
        ReportedBy: gblock@ctoforaday.com


Ok, I'm not sure what the right mechanism for this should be...  Can't even necessarily say it's a bug - 
maybe I'm doing something unexpected.

Our API is trying to cache the contents of its queries over time; what it doesn't necessarily want to do is 
cache the results of its child lists.  We would - but only if, when a new file is added to a collection, that 
collection's ObjectNodes get updated to have the correct results; or at the very least, are notified of a 
change and cleared.

Now I can get around this by disabling the object node's child cache - just use objectCopy() whenever I 
want to go looking for the children, and throw away the copy after I've finished.

Still, it would be nice if there were some way of doing this.  I don't really want to look up the 
ObjectNode each time; on the other hand, I don't want it to cache invalid data.


What's the solution to this?  Do I force the lookup of the ObjectNode each time, and rely on the Slide 
cache to cache the results of these operations?  Is there any way that ObjectNode's contents could be 
invalidated in a way that involves public API?  And can documentation be added to ObjectNode (or 
somewhere else) to describe this behavior and a recommended solution for people like me?

Also, if the cache doesn't invalidate, but the object is serializable, in what circumstances is it 
appropriate to serialize the cache information?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org