> > but TWs containing many Mb of content (both text and embedded images) is > possible >
That was my point, in that his Google Docs paper discusses building something large like wikipedia using GigaBytes to TerraBytes of data. Search and many other features would either fail or be painfully slow. My understanding of search, as implemented, linearly searches through everything and doesn't use saved index trees. If one had millions of records, they could probably take a long coffee break before the search was completed. I just don't see how TiddlyWiki can scale that high without changing major operational components like search regardless of whether the search is performed within the browser or the server. -Doug On Tuesday, April 4, 2017 at 7:25:59 AM UTC-5, Eric Shulman wrote: > > On Tuesday, April 4, 2017 at 4:32:58 AM UTC-7, Douglas Counts wrote: >> >> TiddlyWiki, the app inside the browser, is designed to stand on its own >> because all the content is already contained within it. A user can save >> the file locally and still run it even offline. So your discussions there >> about using a database and building in dependencies upon a website don't >> really fit the purpose/mindset behind TW. You are right in your discussion >> there that no one would want to load all of wikipedia into their computer's >> memory space all at once, but that isn't the mindset behind TiddlyWiki. >> > > TiddlyWiki5 natively supports use as EITHER an SPA (Single-Page > Application) -- where all tiddler content is loaded at startup, and all > changes are local to the browser until the file is saved -- OR as a > client-server setup using nodejs -- where tiddlers are stored in separate > files that can be updated as soon as they are edited (autosave). > > Running under NodeJS, TiddlyWiki5 supports HTTP request protocols that > allows you to "serve" your TiddlyWiki in your browser using either a local > IP loopback and portID (e.g., http://128.0.0.1:8080) or a true remote > host IP and port. The nodeJS client-server architecture also supports use > of "skinny" tiddlers that initially send only the basic tiddler definitions > without the actual content (i.e., just the title, created/modified dates, > author, etc.), and fetches the tiddler content on demand when actually > referenced. In theory, this permits you to create a TiddlyWiki of > virtually any size. In practice, some issues can arise when working with > particularly large data sets. The upper limit depends greatly on the > specific implementation details of your use-case and your system > performance/resources but TWs containing many Mb of content (both text and > embedded images) is possible. > > You can, of course, still save a local stand-alone HTML file from the > TiddlyWiki loaded in the browser, and you can also export your TiddlyWiki > to individual "static HTML" files that can be be published and served > (read-only) from a standard web server, without needing NodeJS. > > enjoy, > -e > Eric Shulman > TiddlyTools: "Small Tools for Big Ideas" (tm) > InsideTiddlyWiki: The Missing Manuals > > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/18b19e8b-0ba5-45d7-905a-a5788f51d537%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
