Results 1 to 3 of 3

Thread: Managing HTTP Requests on Stores, TreeLoaders and Ajax Requests

  1. #1
    Sencha User j-joey's Avatar
    Join Date
    Apr 2008
    Location
    Mersin, Turkey
    Posts
    186

    Default Managing HTTP Requests on Stores, TreeLoaders and Ajax Requests

    Hi,

    I have a couple JsonStores, GroupingStores and a couple TreeLoaders. And some Ajax Requests on button handlers. On back-end i'm using a specialized session manager that changes session id on each request. So simultaneous requests breaks the session.

    To prevent it, i'm using beforeload & load handlers to suspend requests if there is an active one for each request-maker. Is this a good way?

    I'm looking for a centralized way to manage all http requests. Is there a base class that makes those requests?

    If there is, i can extend it to suspend requests if there is an active one.

    or, Is there any other approaches that i should consider without altering my session management?

    thanks already...

  2. #2
    Sencha User
    Join Date
    Sep 2009
    Location
    Calgary, Alberta, Canada
    Posts
    638

    Default

    My question would be, why do you need this? What is the reason behind changing the session id? This poses some serious issues with the crux of AJAX which is asynchronous. XHR or XmlHttpRequest which is part of the core Javascript allows you to do synchronous calls.

    Older techniques forced the client to manage all information for it's session, that is another alternative, but might be cumbersome to manage, and also poses some issues when trying to synchronize the request.

    I believe that each call uses Ext.data.Connection. I am not too sure, but someone asked about making a call synchronous as well. So try doing a search on that. I believe Condor wrote a response on this.

  3. #3
    Sencha User j-joey's Avatar
    Join Date
    Apr 2008
    Location
    Mersin, Turkey
    Posts
    186

    Default

    thanks for your reply enigma.

    right now, i'm facing those serious issues you mentioned.

    i actually hate this session behavior. its purpose is preventing session attacks and it's not my implementation and my plan is to change the behavior to "change id only on fingerprint mismatch" in the future. but, for now, i'm stuck to it.

    i'm going to look into Ext.data.Connection.

    thanks

Similar Threads

  1. Adding HTTP Headers to Direct Requests
    By dancablam in forum Ext.Direct
    Replies: 2
    Last Post: 10 Jun 2013, 5:24 AM
  2. high #http-requests slows down (mainly s.gif)
    By rblon in forum Community Discussion
    Replies: 25
    Last Post: 3 Feb 2010, 1:40 PM
  3. reduce no of http requests for images
    By Ash2009 in forum Ext 2.x: Help & Discussion
    Replies: 6
    Last Post: 20 Aug 2009, 12:28 PM
  4. Adding HTTP Headers to AJAX Requests
    By dancablam in forum Ext 2.x: Help & Discussion
    Replies: 2
    Last Post: 28 Apr 2009, 11:03 AM
  5. Passing http-authenticate credentials to Ext.Ajax or Ext.data.Connection requests?
    By Roland.Bouman in forum Ext 2.x: Help & Discussion
    Replies: 5
    Last Post: 29 Jan 2008, 7:29 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •