Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Jul 2009
    Vote Rating
    Apocalypsys is on a distinguished road


    Default Store - Handling of AJAX responses that came in not same order as requests sent

    I've been using ExtJS for 5 years.
    Recently in ExtJS v3.4.0 i've found an important bug. Particularly i use Ext.Direct but this issue affects all places where multiple asynchronous requests can be handled and returned from server in NOT SAME order as they were sent.
    This problem arises as soon as you begin to navigate in ajax application too fast or server becomes to respond too slow. Then requests A, B, C can produce responses A, C, B. Store does not check if response matches last request sent. This results in situation when you requested one data, but got another one and don't even know about it.
    I have some proposals how this can be fixed.
    In case of Ext.Direct when you call javascript proxy method like YourApi.yourMethod(...) it returns undefined. But it can return transaction. DirectProxy then can save this as lastRequestTransaction property and when handling response check if its transaction id matches id of lastRequestTransaction.
    I have been looking in ExtJS 4.1 and problem is still there. I'm surprised if no one else have seen this issue before?
    Thank you.

  2. #2
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Houston, Tx
    Vote Rating
    scottmartin is a jewel in the rough scottmartin is a jewel in the rough scottmartin is a jewel in the rough scottmartin is a jewel in the rough



    Can you create a report for 4.1 using the following template:

    If there is a problem, I am sure it will be migrated to 3.4.x


Thread Participants: 1

Tags for this Thread