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=42478>. 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=42478 ------- Additional Comments From [EMAIL PROTECTED] 2007-05-24 06:33 ------- (In reply to comment #3) > I see that in the patch, there are changes to the filer interface and its > implementations. Can you summarize non trivial changes to core code - what is > the change and what is the desired effect. Thanks! Sure. The changes were discussed on dev list [1] and include the following: 1. Collection's insert and set are separated. 2. Collection getEntry() method returns Entry class that holds object, its record-level meta and key. This change triggered additional changes in DocumentCache class to store Entries instead of objects. 3. As you noticed, Filer interface was modified and method writeRecord() returns Record instead of boolean. This was done to allow Collection to cache just written record, as it was done before with a plain object, and required meta information to be returned. Also, as a side effect, it allows to store same creation/modification time for the record in meta collection. The previously returned boolean was only actually used in one Filer implementation, FSFiler, but returned value was never checked by Collection anyway, so xml-rpc client would never get any indication that something failed. 4. Filer's readRecord() method got an additional parameter to instruct it to read record metadata only. [1] http://marc.info/?l=xindice-dev&m=117875003317965&w=2 -- 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.
