Sun, Sep 21, 2014
It is a common case in AngularJS to have some model loaded on the main view (like list of objects) and to use these objects in other controllers (like the object details view). Usually it’s done by holding the reference of the list object in other controller scope, to interact with this reference. Until these both objects point to each other (both references point to the same object) it’s very fine. The changes from the details controller are reflected in a list and contrarywise.
But I frequently come across the situation where at least one of these objects is refreshed from the server (eg. in async comet event) and this relationship is lost. A lot of case-by-case code is required to be written to support such instances on the client side.
Thu, Dec 30, 2010
A library for Zend Framework to accomplish common payment gateway workflow, with pluggable payment gateways.