366 karma · joined September 7, 2012
Gmail: paul.ago Twitter: @ago_paul
Now I've wrote my own wrapper to handle retries on the client side so I might give it a try.
Edit: Grammar
A few months ago I hacked a bit with a Zend Framework 1 application and Mongrel2 and it worked well, although zf1 is not the best example given the fact that it was designed to work in a classic mod_php environment where the PHP process doesn't keep its state between requests.
Plus, it doesn't need any external module to work with a specific language, given that ZeroMQ is used to communicate with the backend.
Plus, like someone said, more screenshots or a video would be more explanatory
I think developers should be more aware of how the DBMS works under the hood.
Edit: In my case, I still use row-level lock when implementing the state machine pattern on a model. It enforces the application-level-consistency of the model state, preventing double updates in case of high concurrency, in which the second (concurrent) update would break the application logic.
That is interesting, I was looking for something similar to an EBS for PHP time ago, but eventually I wrote myself an ad hoc solution which uses MySQL (and row locks) plus a gearman worker and cron.
Plus, please use docblocks and document methods and classes.
Given there are some good PHP framework out there already, I would focus on something really new, something missing on the market. Personally, I'm putting down some concepts of a light PHP framework for Mongrel 2
You can easily achieve good performance on some common desktop hardware (or some cheap home-built server) and some SSDs, but obviously, no one would host nothing more than a personal blog on it