From kde-pim Thu Jun 14 12:16:25 2001 From: Olaf Marc Zanger Date: Thu, 14 Jun 2001 12:16:25 +0000 To: kde-pim Subject: eks -- data repository part 1 and 2 X-MARC-Message: https://marc.info/?l=kde-pim&m=99252098515049 hi everybody, i wrote about a new projekt in kde-devel and kde-user, but it might be more accurate to post it here (i'm brand new registered to the kde-pim list). there are some extra issues after this sniplet -------------------------------- i want to dedicate some work to unified data repository effort (i call it eks). my short term goals * get the know-how together (people, structures, state of the art in kde, zope, php), * understand the use of such an effort, * get the structure of data in kde (first kab) documented, * communicate this with zope-projects, * communicate this with PHP projects. the base idea is layed out in an RFC [1] and brief milestones [2]. the first step is to check out competing projects and get a idea of the current effort about a central address book in kde. it would be of great help if i could get a description of the state of deccission making for the * structure of the new address book and * how it is influenced by the qt-3.0.0 db functionality? is there any plan to let kab access other data repositories as * MySQL, * PgSQL, * LDAP, * Outlook-pab files, * Exchange, * ... ? would it help you if i would set up a PgSQL and/or MySQL structure for kab? -------------------------------------------- i look at the whole thing like a underlaying "data-repository-" and "data-traffic-" structure with a unified (two-way-) syncing structure above it (this might be build upon the efforts of kpilot and kandy with syncML in the backround). Mike Pilone [5] pointed out in [4] that he thinks about a more general structure too. a ps file describes some exemplary interaction [3]. only some connections are exemplaryly drawn. the red links are supposed to be the first step (proof of concept). the blue ones would be the "royal" business scalable transportation links. the xml layer would be a * equalizing layer for common access and what is more important * for syncing and * data transfer from one repository to the other. also this layer would allow to use * two repositories at the same time for reading AND writing the compatibility layer would be kio-slaves for translating a xml data into a file format. what do you guys thing about the design? is it possible to implement in reasonlable time? are there major concerns for speed? happy commenting thanks in before olaf [1] http://www.zope.org/Members/maxwest/eks-RFC-0.0.1 [2] http://www.zope.org/Members/maxwest/eks-milestones-0.0.1 [3] http://www.zope.org/Members/maxwest/system-logic-0.0.3.ps [4] http://www.slac.com/~mpilone/kde_pim_api/ [5] mailto:mpilone@slac.com -- soli-con Engineering Zanger Dipl.-Ing. (FH) Olaf Marc Zanger Lorrainestrasse 23 3013 Bern / Switzerland fon:+41-31-332 9782 mob:+41-76-572 9782 mailto:olaf.zanger@soli-con.com http://www.soli-con.com