Macrobyte Resources Conversant Developer Central
Internet groupware development platform
RE: First Look at the Documentation Outline




 
Subject RE: First Look at the Documentation Outline
Posted 7/8/2002; 4:12 PM by Greg Pierce
Last Modified 7/8/2002; 4:12 PM by Greg Pierce
In Response To RE: First Look at the Documentation Outline (#363)
Label High Read 2281
<Previous Next> Thread: Edit Reply
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.

<Previous Next> Thread: Edit Reply
ENCLOSURES

None.
REPLIES

RE: First Look at the Documentation Outline
7/10/2002 by Bradford Powell
Thanks Greg: Yes. I just wanted to note whether a SQL database can be used



 
© 2002 Macrobyte Resources. All rights reserved.