The Source of Quality PowerBuilder™ Information Since 1994
   
 

Hit Counter

Total: 373,079
since: 26 Jan 2005

Latest Podcasts

Interview with Mr TechWave

Thursday, 10 May 2007 6:19 P GMT

Interview with ZapThink

Tuesday, 1 May 2007 1:12 P GMT

Interview with ISUG

Thursday, 19 April 2007 12:16 P GMT

Interview with STUN

Wednesday, 28 March 2007 2:49 P GMT

Podcast Welcome

Wednesday, 21 March 2007 5:07 P GMT

Calendar

««Mar 2010»»
SMTWTFS
  123456
78910111213
14151617181920
21222324252627
28293031

My Pictures

www.flickr.com
ithain's photos More of ithain's photos

My Top Tags

                                       

Search Box

 

Mailing List

LinkBlog Latest items

My RSS Feeds








i(Phone) have my data here... now I want it there!

posted Monday, 9 March 2009

My friend thought on it for a while then said...

Based on what you've written, then I would suggest some possibilities:

1. Wrap any edits to the local database on the iPhone and store the rowId/pk of the changes (for any/all affected changes). Somehow you'll need
to store this extra information to facilitate synchronization. This has its own set of issues since you'll probably need to rely on the user's
clock being set correctly etc. Then you'll need a way to compare those changes to any incoming data as below.

2. You describe "secure updates over the air" but you don't specify what you mean by that. So, will there be a button that the user presses to
refresh the data on the phone?  Or will this be some kind of background thread?  How often will updates be synchronized? Does it only connect
via Wi-fi or is cellular reliable enough to sync, etc. Will you use https with an XML payload or are you going to write some kind of custom socket
level stuff to handle secure communication?

3. Since there are no native database client libraries for all practical purposes then maybe you'll need to invent a web service for updating
modified records and downloading new updates. What do you do when there is a conflict between what the user has chosen and the updates coming in?

4. At which point, depending on the size of these databases, you might have been better off implementing an intermediary web application/middle
tier that handles the actual synchronization, since it is complicated...

The conversation paused, with my head spinning. Dude I don't want to do any of that, I thought to myself. You're right, it's hard and I just want to
concentrate on my business problem. I know the Enterprise Database I want to synchronize with and I know the subset of tables, that I want on my
iPhone.

Luckily for me iAnywhere plan to extend their reach by targeting iPhone support for early summer 2009. The UltraLite database has some similarities
with SQLite. Both are in-process databases, they are of similar size, similar performance and have a similar range of SQL. The big differences are
that UltraLite has Enterprise-ready features such as a built-in synchronization client, and security. This security can be through obfuscation or
strong encryption of the actual database itself as well as the synchronization process.

Phew I don't have to re-invent the wheel... Worms back safely in their can!

Interested? Register your interest at http://marketing.ianywhere.com/forms/SQLAnywhereiphonesupport

Ian

 

iAnywhere have the leading mobile database and synchronization technologies, that enable data to be shared and updated between
the enterprise and remote users - SQL Anywhere, which drives some of the largest mobile database deployments in the world. SQL Anywhere databases
already support a wide range of handheld devices and smartphone platforms, including Windows Mobile, BlackBerry, and Palm OS.

tags:      

links: digg this    del.icio.us    technorati    reddit