| 3 | | 'See [http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/45bf58ccfeeabc92/3f47c6e92d5b8855 this discussion] on tiddlywikidev'' |
| | 3 | See [http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/45bf58ccfeeabc92/3f47c6e92d5b8855 this discussion] on tiddlywikidev'' |
| | 4 | |
| | 5 | == Background == |
| | 6 | |
| | 7 | There are three distinct ways in which TiddlyWiki can interact with a server: |
| | 8 | 1. the server can generate a TiddlyWiki file with baked-in content. Usually, this means marking up empty.html so that it can be treated as a template into which tiddler text is spliced from, say, a database |
| | 9 | 2. the server can participate in TiddlyWiki's infrastructure for importing, exporting and synchronising tiddlers between occasionally or manually connected stores |
| | 10 | 3. the server can take over key TiddlyWiki operations to give the user the semantics of a traditional shared wiki |
| | 11 | |
| | 12 | This discussion is chiefly concerned with the third category, but they overlap somewhat - these servers would still use the first technique to splice their machinery into the TiddlyWiki file. |
