Is there some documentation on the format of the POST variables sent from the Dataprocessor from both the normal 3.6 Scheduler and from the Mobile Scheduler?
I had created my system using the normal 3.6 Scheduler and the Dataprocessor, and created a PHP file to handle the POST data from the Dataprocessor and to return a valid XML response.
The documentation for the Mobile Scheduler states that the server side logic is the same for both normal and mobile scheduler, but when I tried to integrate the mobile scheduler with my system, I discovered that the data being POSTed is different for the two systems.
From the normal 3.6 Scheduler, I get POST data like the following
If I have read the documentation correctly, then if I change my normal scheduler code to say
dp.setTransactionMode(“POST”,true)
then it will add the ID number to the front of the name of each data field POSTed, and then both my normal scheduler and mobile scheduler will use the same format.
Yep, also, if you are including dhtmlxconnector.js on the page ( which is the part of dhtmlxscheduler.js by the way ) it will switch to send-all-at-once automatically. You can call setTransactionMode to switch it back to send-one-by-one mode
If I set the scheduler to use “send-all-at-once” so that I have the IDs prefixed at the front, AND I use the dhx.proxy, what will happen after usage offline when dhx.proxy detects a connection is available?
Will the server get any duplicates?
Also what would happen if a user updated an event that hadn’t yet been inserted - would the dhx.proxy just send one INSERT with the updated info?
Connector supports both formats, but for greater compatibility it must be “inserted”
If I set the scheduler to use "send-all-at-once" so that I have the IDs prefixed at the front, AND I use the dhx.proxy, what will happen after usage offline when dhx.proxy detects a connection is available?Will the server get any duplicates?
Nope. Proxy intercepts data a step before formatting, so used data interchange format doesn’t matter. Proxy object will combine all data saving requests to the same object in the one request.
Also what would happen if a user updated an event that hadn't yet been inserted - would the dhx.proxy just send one INSERT with the updated info?
Yep, insert + update will result in single insert operation.
I’m not using the connector, as I need some quite extensive custom handling, so I’ve created my own handler at the server end, and it can now deal with either insert or inserted and can also handle either single or multi POST operations.
From how you explained the Proxy will operate, I should be able to add that to my system without needing any further changes at my server end.
Thanks for your help.
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan