On Mon, 08 Jul 2002 16:58:14 -0400, Bradford Powell wrote:

>Is twine part of Conversant, or exactly how does this fit in.

Twine is really separate application on which Conversant relies.

Twine provides application programming interfaces ( APIs ) for storage and other services which Conversant uses.

The key to Twine is that each of it's APIs reside on-top of "engines", which are essentially plugins to interface to actual databases. The default engines store data in Frontier/Radio table structures -- but other engines could also support anything from storing data in the file system, to mySQL, or whatever other datastore is desired.

This makes the actual data storage invisible to Conversant, so the "engine" used by a particular zone or conversation can be changed w/o effecting anything running on top of it.

Does that make sense? It's hardly full documentation, but that's the general idea.

g.