Hi, thanks for the links with information. I thought that, since tiddlyweb is a reference implementation, that it was the intention to have a lot of different backends. So its not against tiddlyweb, its for the tiddlyweb specification that I am interested in it. Different server implemantations of the api may also help in testing it and making better.
My intenttion in the server backend is to use TW as the presentation layer for a lot of different data. So the server internally will deal not only with tiddlers, bags and recipes. It will format data that they can be read by TW. In some way it is similar to the tiddlyweb data project. On a user oriented perspectieve I aim for a simpler distribution of the backend, i.e. single file (for desktop use included simple http server, for server use as single cgi/scgi/fcgi). This is at least possible with TCL starkits. Experimentally I did this with T'swiki, an old server side for TW using TCL and SQLite. As I see it, it is a server backend with a different emphasis. A backend that can be used on a desktop and a webserver, or on a mobile. Maybe (this is a future dream) TW can be integrated with phonegap to have it running on all kinds of mobiles. When this happens it is very handy to have the same api, as switching between backends is then quite simple. vlak -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
