Now it looks much easier for me, thx a lot

Honza

On 18 lis, 15:29, Daniel Drozdzewski <[email protected]>
wrote:
> On Thu, Nov 18, 2010 at 2:13 PM, biokys <[email protected]> wrote:
> > Hi Daniel,
> > thx for your post
> > my goal is to make data sharing among any users so they can store
> > their information locally in SQLite (in case of no network connection)
> > and when they want, they can synchronize these datas with central
> > datastore (Google app engine). so i assume, that transactional
> > behavior is not crucial in this case, but can be handy.
>
> > Honza
>
> Hey Honza,
>
> That is true, you don't need a transaction that would span both interactions.
> It would be 2 separate transactions, or to be precise 1 local
> transaction and server upload would be the best effort kind of thing,
> with the assumption that it will eventually work at some point in the
> future (could be quite distant future in terms of transactions).
>
> All you have to do is to have some sort of time stamp attached to the
> data in both places and the server routine will ask only mobile for
> the data since its latest time stamp.
>
> --
> Daniel
>
>
>
>
>
>
>
>
>
>
>
> > On 18 lis, 14:47, Daniel Drozdzewski <[email protected]>
> > wrote:
> >> On Thu, Nov 18, 2010 at 1:05 PM, biokys <[email protected]> wrote:
> >> > Hi, I am trying to find out, how to store data in a local DB and
> >> > remotely over HTTP in one transaction. Does exist any native mechanism
> >> > in Android phone for transactional behavior?
>
> >> > Thx Honza
>
> >> Honza,
>
> >> Short answer is: I don't think so.
> >> In order to achieve this, you would need to look at Distributed
> >> Transaction Coordinators, if you require full transactionality.
>
> >> Java EE has JTA (Java Transaction API)  but it's not present on mobile
> >> platforms. To achieve this it relies on few very crucial things:
> >> - JDBC 2.0 drivers for each data source you need in your distributed
> >> transaction that actually implements XADataSource and XADataConnection
> >> - JEE Application Server
>
> >> Android API mentions XADataSource and XAConnection, just have a look
> >> at javax.sql.DataSource documentation, but there is nothing else. I am
> >> pretty sure that SQLite does not support such mechanisms, but I could
> >> be wrong.
>
> >> You can try doing it the garage way:
>
> >>    db.beginTransaction();
> >>    try {
> >>      //send data to SQLite
> >>      //send data to external service
> >>      db.setTransactionSuccessful();
> >>    } catch (SQLException) {
> >>       //error in DB: contact the server to revert the commit and hope
> >> it will do it
> >>    } catch (IOException) {
> >>       //error with the external server, and you have no guarantee,
> >> whether it has been written or not
> >>    } finally {
> >>      db.endTransaction();
> >>    }
>
> >> As you can see, you can have guarantees only about the internal SQLite
> >> database. As soon as you involve network in your transaction, things
> >> get orders of magnitude more complicated.
> >> I am not sure, how strict are your requirements on transactionality.
> >> You could also implement some timer on your server that is
> >> transactionally persisted to a DBMS on that server, so that crash +
> >> restart or network outage would not cause it disappear. They you would
> >> revert any uncommitted transactions after some timeout. That gets you
> >> somwhere, but I am pretty sure it will break in some scenarios.
>
> >> --
> >> Daniel Drozdzewski
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" 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/android-developers?hl=en
>
> --
> Daniel Drozdzewski

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en

Reply via email to