Re: Database Persistence

Hi Eric,

we had this discussion a while earlier - in essence pebble currently is meant to be quickly set up and a neat small blog engine that does not have ambition to provide enterprise scalability (e.g. clustering etc.) - for that purpose the current storage engine is quite ok.

If nobody else replies and states otherwise you can safely assume that no work is being done for providing a database backend. I'm assuming that nobody objects this work to be done and it can also be included with the product if the default setup stays as simple as it currently is. The users that have chosen pebble have done so for exactly this reason. But I guess nobody would object having other possibilities should they ever want them.

But first you might ask yourself why you actually want to do the work - scaling, backup, enterprise-acceptance, just-being-used-to-it come to my mind as possible reasons.

Let us know what you're about to do, but don't expect too much enthusiasm here to change the backend. But go ahead as long as you keep it simple :)

Olaf


On 16.08.2011 18:26, Eric Sheridan wrote:

Team,

Thank you for all of your hard work and dedication to the Pebble
blogging project. I see the persistence layer is implemented using XML
files. Are there any alternative implementations leveraging a database
of any kind? The DAO abstraction is certainly clean enough that it
wouldn't require a significant effort on my part but I would prefer not
to duplicate effort.

Thanks!

-Eric

------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2

_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user