RE: [Pyblosxom-devel] Supporting comments, etc.

[Blake W. <bl...@ph...>]

> Sorry, the XML we were discussing about only relates
> to importing and exporting data between storageAPI
> compliant objects.

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.

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.

(And I think that picking one or the other is better than
 having both, from a small-api point of view at the very
 least, as well as from the no-duplication-of-functionality
 point of view.)

> > How does blosxom and the other *osxom systems store
> > data?  Would we want to store our data in a compatible
> > format further enabling folks to switch between *osxoms?
> There's no common way.

Bummer.  :(  I guess if there was a single way to do this,
we would already have done it.

> 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.

Later,
Blake.