Need help porting Prevayler (Java) to Python

[Patrick K. O'Brien]

[Michal Wallace]
> I like the idea of persisting the commands, but the idea of
> writing your own for every Add/Insert/Delete seems to be
> java nastiness to work around the static typing.
>
> I don't think I would port it directly; it's just not very
> pythonic. Instead, wouldn't you want something like:

I was planning to make it more Pythonic/transparent after it was ported.
There is more than one way to approach the issue of transparency and I was
thinking that one or more solutions should be able to be layered on top of,
or in addition to, the default command mechanism.

> Anyway, doesn't ZODB do all this?

And more. But ZODB isn't pure Python (uses some C code and therefore
requires a C compiler or compiled binaries) and is a bit complex for some
situations. That's not to say that I think there is anything wrong with
ZODB. I don't. I was just looking for something simpler and Prevayler caught
my eye. I figured I'd start with the Prevayler approach and see
if/where/when it breaks. I think there is room in the Python persistence
domain for an approach like Prevayler. It strikes me as fitting nicely
between pickles and ZODB. PythonCard applications, for example, might
benefit from a Prevayler type approach to persistence. And when you add Pyro
(Python Remote Objects) to the mix, it could get really interesting.

Pat

--
Patrick K. O'Brien
Orbtech
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------
Web:  http://www.orbtech.com/web/pobrien/
Blog: http://www.orbtech.com/blog/pobrien/
Wiki: http://www.orbtech.com/wiki/PatrickOBrien
-----------------------------------------------