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

[Wari W. <wa...@ho...>]

will wrote:

>The disadvantages to using XML would be that the performance of
>loading/saving is probably an order of magnitude slower than pickling.  
>In addition to that, we also take on the burden of architecting the XML
>format we want to save in and how it works.  We definitely get more bang 
>for our buck with pickling.
>  
>
Sorry, the XML we were discussing about only relates to importing and 
exporting data between storageAPI compliant objects. If I don't like, 
say a file based storageAPI system, I can export to the pickle, and get 
the sqlite storageAPI object to get the data from the pickle export and 
store data in it's database, this is so that you don't lose data while 
changing 'drivers'.

>The advantage to using XML is that other non-Python processes can 
>manipulate the data.  I can't really think of other advantages--though it 
>should be noted that this is somewhat of a big one.
>  
>
Since this is a dump() and load() methods, maybe later we can define an 
export() method to export to a documented format like XML or maybe 
MovableType style comments data. A dump() and load() is for pyblosxom 
and pyblosxom only I guess (though other program could use its data)

>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, Rael's blosxom uses a modified standalone 
trackback tool for comments (which uses perl style dumps), I'm not sure 
what Sam Ruby uses, phosxom uses sqlite to store feedback. For pyblosxom 
I want it as flexible as possible yet can migrate data as well. Data 
storage is one thing, exporting it is another.