[CLOSED] Aborting Transactions

Page 2 of 2 FirstFirst 12
  1. #11
    I don't mind making an example but the problem is with the face I use remote calls to a DB (which is where the problem ls) and I don't now how I would produce an example with a remote DB which you can use.
  2. #12
    Well, I don't think the abort method deals with database transactions.

    It deals with AJAX requests that you send from a client to a server.

    So, I think a database should not be required to reproduce this problem.

    Please try to use some test data instead of the database.
  3. #13
    Hi Daniil,

    Thanks for all the help, I've now come up with a solution this problem so you can mark this thread as closed
  4. #14
    Nice.

    We would appreciate any details about the final solution.
  5. #15
    Hi Daniil

    The solution isn't exactly what I wanted but works. Once a user clicks on a row I lock that row using the selecitonModel and then start a task which runs 150 milliseconds. The task checks to see if the all the store requests are completed for that row, once they complete I unlock the row. To achieve the smooth transitions between row I check to see if the user stays on a row for longer then 1 second if they do I fire off the load request. If they move of the row before the second is up I don't bother firing the load on the stores.
  6. #16
    Thank you. I think it is a good solution!
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Replies: 0
    Last Post: Sep 17, 2009, 8:04 AM

Tags for this Thread

Posting Permissions