Version 2 (modified by MartinBudden, 7 years ago)

--

TiddlyWiki Server Side

'See  this discussion on tiddlywikidev

Goals

To have a common server API that means you could link any client (from a full serverside TW plugin, to a tiny TW plugin to save Minesweeper scores to a common server, to a TiddlySnip-type browser extension) to any server (db-backed with versioning services like ccT and ZW, a read-only plugin repository, etc etc).

TW shouldn't really require it's own custom server implementations, but rather should use industry standard protocols to exploit existing servers. For example, Amazon's S3 and similar services expose commodotised data storage that is suitable for TiddlyWiki as a file-level storage medium. Similarly, Zope provides a commodotised content management system that TiddlyWiki can use as a tiddler-level storage medium.

Architecture

JavaScript? APIs

 http://code.google.com/apis/gdata/protocol.html#Additional-resources

 http://www-128.ibm.com/developerworks/xml/library/x-atom10.html