> - there is another important point, this person must also master eZ Publish > cluster, and this is not > a piece of cake. The code is pretty easy but the matter is on the design > level, we are dealing with > some really important problems (concurrent writes under very high load for > example) sometimes and > we must avoid making thoses mistakes again while switching to ezCPO. The original mail didn't say anything about Persistent Object afaik. Only the Database component. Those two are not the same at all, and the first does not imply the other.
Frederik -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
