Hi Stefan, > Thousands of wiki files indexed in a main wiki can consume the system > memory and freeze the browser, I suppose. >
Surely, there are limits to any approach. For thousands of wikis I would not expect any browser based approach to work that aggregation well. This would call for an entirely different stack of interlinked software processes, both on the model end (database) and the controller (watching for changes to individual wikis and triggers or pushes updates to the global aggregation). So, if you want to manage "thousands of wikis" that way, I'd argue neither TW2 nor TW5 cater for your needs in their browser based version. Best wishes, — tb -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e0da2041-6310-41cc-bb67-de75d2feca84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
