TiddlyWeb Stores and Serializers

[chris...@gmail.com]

For those that are curious about how TiddlyWeb works and some of the
ways in which it can be extended, I've written some a bit silly and
weird but hopefully informative blog postings that relate to the
storage and serialization mechanisms in TiddlyWeb.

The first one explains how to use one TiddlyWeb server as the backend
storage mechanism for another TiddlyWeb server by creating a new
implementation of the StorageInterface. It's called "Webs of
TiddlyWebs with TiddlyWebWeb"<http://cdent.tumblr.com/post/46209623/
webs-of-tiddlywebs-with-tiddlywebweb>.

The second explains how to use to use the SerializationInterface to
get TiddlyWeb to send TiddlyCake to Fred. It's called "And the Leaders
said, 'Let Them eat Cake'"<http://cdent.tumblr.com/post/46434732/and-
the-leaders-said-let-them-eat-cake>.

If there are TiddlyWeb curious people out there, I'm eagerly seeking
input on where to take the system next, and what questions need to be
answered. People get in touch with me.

Thanks.

[Martin Budden]

Chris,

by the way, I agree with your approach of separating the serializers
from the objects they serialize. Long experience has taught me that
giving objects serializer member functions, although superficially
attractive from an object-oriented perspective, causes problems of its
own. Having the serializers separate means:

i) the objects don't have to be extensible to support the addition of
extra serialization methods
ii) tends to lead to better documentation of the serialized form of the object
iii) funnily enough also tends to better object encapsulation, since
the serializers cannot access the private members of the object and so
cannot inadvertently expose the internal structure of the object in
the serialized form
iv) tends to result in using a standard rather than something
proprietary for the serialized form of the object

Martin

2008/8/19 cd...@peermore.com <chris...@gmail.com>: