This plugin establishes its own interface to communicate with ZC through AJAX; however, as of ZC 1.5.4, there has also been a framework variable available of zcJS that supports similar communication with a number of "built-in" features.
This plugin uses XML to communicate with the server; however, to obtain/use related data "cleanly" the same information needs to be made available in JSON form in order to be processed by zcJS "properly". The current plan is to maintain the existing method as a possibility for "backwards compatibility" but to also make it available in JSON for "future" versions. Technically all of the data could be collected in one format and then processed accordingly, but with the age of this plugin it seems like changing that data structure could be problematic for other versions in the wild. Ideally, the JSON data structure could be picked up and used as necessary to support those other alterations, but doesn't need to do so right now.
This plugin establishes its own interface to communicate with ZC through AJAX; however, as of ZC 1.5.4, there has also been a framework variable available of zcJS that supports similar communication with a number of "built-in" features.
This plugin uses XML to communicate with the server; however, to obtain/use related data "cleanly" the same information needs to be made available in JSON form in order to be processed by zcJS "properly". The current plan is to maintain the existing method as a possibility for "backwards compatibility" but to also make it available in JSON for "future" versions. Technically all of the data could be collected in one format and then processed accordingly, but with the age of this plugin it seems like changing that data structure could be problematic for other versions in the wild. Ideally, the JSON data structure could be picked up and used as necessary to support those other alterations, but doesn't need to do so right now.