> > I said the other day that I think there are really four or
> > five parts to this project. I suggest we split into the
> > following groups (with associated mailing lists):
> >
> > * Database (cdin-db) - focuses on the database, its content,
> > and its storage issues. Selects hashing algorithm.
> > * Server (cdin-server) - focuses on the server software, and
> > interfaces to clients, database, other servers
I believe there's sufficient breadth in each of these to warrant
separate discussions, and at least the DB area (my personal area
of interest) is not resolved yet.
cdin-db may not even consider the actual database used (thats really
a server implementation issue), but would be purely concerned with
the database *content*, the format and interrelation between database
records and fields, level of detail etc. The hashing algorithm
would be part of this.
How the data is stored, served and distributed (heirarchical structures
with master DB's propagating to slave DNS mirrors or whatever) is quite
separate and has it's own array of issues.
> I have set up three new cdin.org mailing lists: cdin-server, cdin-proto,
> and cdin-client.
An excellent start.
> If people feel that cdin-db and cdin-distro are needed, then I'll set
> them up. I'd recommend against going overboard, though, and defer that
> choice for later (if/when the server traffic is too much).
IMHO I'd like cdin-db :) What do people think?
> Personally, I don't think that I'll cross-post between the cdin mailing
> lists (otherwise, why split them?).
I totally agree. I'm looking forward to settling down to my *one*
mailing list of primary interest.
> > I re-volunteer, as I did Monday (or tuesday, I forget) to be the
> > stuckee--er, coordinator--for the DB group.
David, how 'bout it?
Cheers,
Brian.
-- ----------------------------------- Brian Murray Proximity Pty Ltd http://www.proximity.com.au/~brian/ -----------------------------------