Re: Re: Persistence extension

So basically you created a database driven session. The way I look at it persistence of data is not a issue and there are already multiple solutions for this. True persistence would cover not just data but objects and resources. This is the true "gift" of persistence in say JAVA for example. You do not need to recreate objects, reconnect to databases, and rebuild file and other resources. You can't just store these things for access later without rebuilding them in PHP, which takes away the benifits of persistence to begin with, Performance. maicon@edu.ufrgs.br wrote:

some more details I wrote an object-oriented persistence framework for databases in php ( like PEAR::DB_DataObject and a lot out there). It uses PEAR::DB as it's database-abstraction layer. The solution works well, but is slow. Then I think to write a extension to boost the performance. This extension will use the PDO extension as is database abstraction layer. I also plan to optionaly use the memchache extension within the persistence layer, with a very clean interface(almost invisible) to the programmer with a very large gain of performance. Maicon Citando "M. Sokolewicz" <tularis@php.net>:

maicon@edu.ufrgs.br wrote:

Hi! I'm Maicon, from Brazil. I'm thinking in write a persistence extension and post it in pecl.

what exactly *is* a peristence extension? what does it mean (according to you?), what would it do/provide?

I would apreciate any sugestions and critics.

suggestions... about...? critics.... on your idea? It's hard to be critical, since I have no clue whatsoever what your idea is...

Sorry about my poor english... Maicon Federal University of Rio Grande do Sul ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

-- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

------------------------------------------------- This mail sent through IMP: http://horde.org/imp/