BJ, That's pretty much close to the solution (hack) I gave to the classic wiki a few years ago. Back then I was a bit worried about mobile access (yeah, I use my wiki everywhere) because each time the wiki loaded (and I have several wikis) the entire html was served. I went into dissecting the stock HTML and putting the entire javascript in a separate file. That way it was cached by the browser, and only a small(er) HTML file was transferred, containing only the tiddlers.
I've seen tiddlywiki 5 boasting 1.5 Mb of data transfer for an empty wiki. That's quite a lot even nowadays. Refreshing my wiki 10 times a day, it means 450 Mb at the end of the month (ouch). I now have around 6 different wikis (I use them as notebooks for different subjects). And the url is used internally to select the database. I even have a coarse access control list (for the entire wiki), so some users can access some specific wikis. I wish I can add all these features into tiddlywiki 5. That will be the only way for me to switch. I still don't understand much of the massive piece of code the new tiddlywiki has become. I want to keep as much of the original code as possible (both in the server and the client side). I really like your idea, as long as I'm able to intercept load, save, and delete. I would also like to expose the functions from the same http server that is already running. But I have a doubt, what will I loose if I leave the system tiddlers to be loaded at start? Would I gain something if I delay the load of specific system tiddlers until needed? I'm really new to tw5. I know tiddlywiki tries to store everything in a single file, but that only seems useful when you're editing local (the only way available at tw genesis). For a server version it has no use, and actually, it makes it harder to cache. Would it be too hard to modify the code so it will serve a few javascripts and the HTML? -- 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 http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
