Hi Benjamin, On 07/27/2010 09:52 AM, Benjamin Eberlei wrote:
> i already have a buggy and untested prototype of the CouchDB backend > that is as small as 300 loc. I think an additional abstraction of the > document > layer may only complicate the implementation or just lead to all API > methods being delegated to yet another backend. Its probably easier to > just have an additional ezcWorkflowMongoTiein that is equally thin. > > Regarding the non-Update only Insert, ezcWorkflowDatabaseTiein operates > exactly the same. Yes i have very long running workflows that may change > often, so this is an important requirements (for me). But i think this > behaviour is important for short workflows of just some minutes execution > also. I'd love to see your CouchDB back end for Workflow as a WorkflowCouchDBTiein or something. I agree with you that abstracting the back end once more introduces to much complication. Workflow already provides the interface methods, so that should work out fine. Could you provide small requirements and design docs? Regards, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
