|
From: Wari W. <wa...@ho...> - 2003-02-06 16:48:06
|
Blake Winton wrote: >Really? I figured we would use the same API to handle >both storageApi compliant objects and external systems, >since I think people will switch between storageApi >systems about as often as switching between non-pyBlosxom >and pyBlosxom systems. > The thing is, how do you get people to use the same data format with differing comments system out there. If you want something that works with all *osxoms, then you need something standalone and outside of pyblosxom, like what Rael did with the Standalone Trackback Tool, or something like quicktopics on steroids :) >Furthermore, if we had export() and import(), then dump() >and load() wouldn't give us any extra functionality, so >if we only get to pick one, I would choose export/import. > > Ok, based on my previous mail, XML format is the way to go to exchange data when we need to migrate. >>For pyblosxom I want it as flexible as possible yet can >>migrate data as well. Data storage is one thing, exporting >>it is another. >> >> >But migrating it from one driver to another seems to me to >be very similar to migrating it from one system to another. > > We just need a well documented XML format then, agreed? |