Blocking issue with AJAX using JQuery -


Try again Do not think I have questioned clearly.

The big problem is contracting with the company, I have been delayed loading using AJX to convert from site to me. To do this, I am using page methods to load control. Javascript looks like this ... works like a winner!

  $ (document) .ready (function () {var clientID = '#' + '& lt;% = BackUpPower.DivBackUpPower.ClientID% & Gt; if ($ (client id)) Data type: "Application / Jason; Charset = UTF-8", Data type: "Jason": {$ .JAX: {Type: "Post", URL: "Dashboard. Espacks / Getback Controll", Data: "{}", Content Type: ", Timeout: 15000, Success: Function (result) {$ (Client ID). CSS ({" Display ":" None "}); $ (Client ID) .removeClass ('Load'); $ (ClientID) Attr ('innerHTML', result.d); $ (clientID). FadeIn ("slow");}, error: function (xhr) {// Warning ("GetBackUpControl Failed");}})}}  

});

The server-side code looks like this ...

[WebMethod]

  public stable string GetBackUpControl () {page page = new Page (); UserControls_BackupPowerForm CTL = (UserControls_BackupPowerForm) page.LoadControl ("~ / UserControls / BackupPowerForm.ascx"); Ctl.ID = "Backup Power"; Page.Controls.Add (CTL); Ctl.HostPage = "Dashboard"; Ctl.ActiveTimeRange = Time limit.LordMonth; Try {ctl.DataBindChart (); } Catch (exception was caught) {logging adapter. Logger error (caught message, "inducing generating chart", caught); Return string Empty; } Stringworld author = new stringwriter (); HttpContext.Current.Server.Execute (page, author, incorrect); Return Author Toasting (); }  

The problem occurs when a long-running callback is in progress and the user tries to switch pages by clicking on the hyperlink, before the system does so long Waiting to move through the code I see that the callback is properly revoked on the new page request and the JQuery error handler, but still looks like a new page request to complete the callback. Waiting. If no callback is in progress then the new page request is immediate. Anyone know what is happening?

Thanks for the help Turn-out problem was to do with asp.net seriallase page requests, which Uses the session to prevent updated conflicts. Setting Resolutions to "Redonially" in Page Direction Hull problem However, if the page turns on sessions, then this will be a problem. An alternative solution for this is to post the post on the second page, which allows session updates.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -