> I'm going to look at the wikitalk library to see if I can alter it so > that it gets all the topics (fast), then prunes it, then sorts it > (slow) to see if I can fix my particular problem, but I thought that > I'd share what I have been seeing. >
I got this to work (times down to 500 ms,) but I had to expose the CompareModificationTime to be public so that I could get a sort after a fetch as opposed to doing it in one step. Is it overly offensive to make this method public? If so does anyone have any other ideas on how I can do this? Craig, I also have a question about this whole mechanism. The AllTopicsXxx methods work by getting the Topic list and then, if provided, applying a sort to the results. Why does the sort need to go deal with all the security stuff again? seems like the fetch would have handled that in the first place... Am I oversimplifying or missing something here? -nathan ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/flexwiki-users
