A bounty, eh? That's why I'm trying to learn all I can about e-d-s. My wife and I have sufferred for far too long to not have a shared contact db.
We've been thinking about this a lot and do not think that much of a schema is necessary. Since the client does most of the work anyway, the problem quickly reduces to a dictionary. It kind of disappointed me because I enjoy databases. I'd rather have this done, though. As far as the connectivity information, I think the following would suffice: 1) a URI/URL 2) username/password > we have a bounty for a contact db backend. what > sort of information > would we need for that? db server hostname, port, > database name, user > password? Assuming of course the schemas are > hardcoded. > > Chris > > _______________________________________________ > evolution-hackers maillist - > [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution-hackers __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
