> So after pondering this a bit, it seemed even more reasonable to just > supply AllTopics with the FilterDelegate (or SelectionDelegate > depending on if we wanted to specify what to remove or what to keep) > and then this behavior is all kept in one place. So now my code looks > like this > > QTNC qc = namespace.AllTopics(ImportPolicy, SortDelegate, > FilterDelegate); > > Strictly speaking, we are adding nothing to the core. I could very > easily write a SortDelegate that did exactly what > CompareModificationTime does if it is not exposed. I can do the code > my second example myself. It just seems quite reasonable that I'd be > able to do the third bit as well.
OK, that makes sense. It even leaves the door open for us to improve the content pipeline later to support filtered and sorted queries in the content pipeline - one can imagine in the distant future the SQL Provider being smart enough to create an optimized SELECT statement. But later, later. :) It sounds like you've already written this. If you have tests for it, I'd say go ahead and commit it. Thanks for taking the time to catch me up. :) Also, assuming we make this change, is it fair to say that your current analysis is that FW 2.0 is fast enough for you? There are still a bunch of critical use cases I need to verify (David's mega-wiki among them), but since you were one of the people who had specific criteria, I just want to make sure that we've at least addressed your scenarios. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
