We are currently using a technique of connecting our DataBoundControls to a PHP backend, transport via JSON over httpMethod POST, and encoding the JSON on the server side with a Zend Json encoder for return to the client. We use this same technique in places also with RPCManager, to make requests outside of a DataBoundControl.
We occasionally run into "namespace" issues due to the "flat" nature of POSTing the data. For example, if we need to transport a row ID and some other record ID, we need to name them differently to avoid naming conflicts, even if semantically it makes little sense to do so.
So the question arises. We can pass more complex data structures if we use WSDL binding instead, and utilize a SOAP package with PHP on the server. In terms of performance, which is critical to our app (keeping response times low and bytes over the wire minimal), are we better off using the less elegant solution we have now? Do you have any sense for the performance overhead when using WSDL?
Thanks for any input you can impart
Pete
We occasionally run into "namespace" issues due to the "flat" nature of POSTing the data. For example, if we need to transport a row ID and some other record ID, we need to name them differently to avoid naming conflicts, even if semantically it makes little sense to do so.
So the question arises. We can pass more complex data structures if we use WSDL binding instead, and utilize a SOAP package with PHP on the server. In terms of performance, which is critical to our app (keeping response times low and bytes over the wire minimal), are we better off using the less elegant solution we have now? Do you have any sense for the performance overhead when using WSDL?
Thanks for any input you can impart
Pete
Comment