Although Convertigo MEAP supports SQL connection to the back end, synchronization is not the preferred process to use with Convertigo. The primary goal of the Convertigo is to provide transactional web service methods on back end application (Including of course SQL).
Nevertheless, If you would like to do synchro, this is completely possible using the web services interfaces.
For scenario1 (Pull), just write a getNewLines sequence/transaction returning all the new lines you have in you sql database. On the Sencha Client side just insert in the localdatabase all the new lines you receive when you call a the getNewLines sequence. To insert in the localdatbase you can use Sencha's localStorage store.
For Scenario 2(Push), This is also possible. Convertigo server can automatically launch sequences/transactions using it's integrated scheduler. see www.convertigo.com/en/product-overview/c...tration-console.html
The polling using this sequence ends up with a SQL call to the database and the data returned can be inserted in Convertigo Cache.
When a Mobile device connects it can execute the same Sequence and the data would be returned from Convertigo Cache instead of the SQL data base. Again , you can use Sencha's localStorage to update the local database on the mobile.
These synchronization mechanisms are to be implemented by the Mobilizer programmer. there is no standard SDK/library for that but this would not be a bad idea : )
Convertigo Mobilizer is OpenSource we would be glad to add a type of "Synchronizer" project in our project Library.
By the way, (Not critical
)you posted in the "announcement" section of the forum. Cloud you please post in the appropriate section?
Hope this Helps
Convertigo Support team.