Client and server being coupled? Maybe I'm not as familiar with the
term as I thought, but I'm not sure how else to access the local
SQLite DB that resides on the device itself. With the javascript db
transactions being async, they were colliding and causing all sorts of
problems. "Deferred" relieved much of that headache.
This is a web application that uses the HTML5 local DB to collect data
from the database server and store it locally for use offline. And
yes, all transactions with the "online" database server are handled
seperately via ajax. When the user is done updating his/her data in
the offline database, the connection is checked and new, modified data
is sent back to the database server when available.
So, I guess I am coupled with the local DB in that regard. Is there
an alternative that I wasn't aware of?
Scott.
On Jun 5, 2011, at 6:58 PM, Garrett Smith wrote:
On 6/5/11, Scott Kallen <[email protected]> wrote:
Well, my question was about whether or not anyone has broken it up,
not the merits of using it.
I've committed to using the new deferred functionality in 1.5, which
was a savior when doing SQLite calls.
The client and the server should not be coupled. IF they are, you've
got more porblems then jQUery.
And sure, I could spend the
time to roll my own for all the functionality,
Functionality to do what?
--
Garrett
--
You received this message because you are subscribed to the Google
Groups "iPhoneWebDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en.
