AjaxManager.SetMaxRequestQueueSize with Prometheus

[paulo.galão]

Hi there,

I was just wondering... what happened to SetMaxRequestQueueSize on Prometheus' AjaxManager?
Did it just go away or are there any alternatives?

Thanks,
Paulo

[Steve]

Hello paulo.galão,

Unlike the previous version of RadAjax, multiple requests are no longer supported - this is another ASP.NET AJAX limitation. E.g. if you start one request, subsequent are ignored until the first response is received.

All the best,
Steve
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[LeBear]

I've put together a good mechanism for queuing Ajax requests on the client.  As such, when an Ajax request is initiated, it is added to a queue.  The queue is constantly checked and if something is waiting, and the Ajax "connection" is available, it initiates the request.  Works like a charm.

My question:  Is it still the situation that multiple Ajax requests are not supported as previously stated, and if so, are there any plans to implement your own queue?

Personally, I like my queuing mechanism and I'd hate to have to remove my code - but then again, I guess I'd be ok with not having to maintain it, either.

Thanks.

[Steve]

Hello Barry,

Let's not forget that Prometheus is still in Beta although with Go Live license. We do have quite a few aces in our pockets and what you see now is definitely not the final product which is going to be official in Q1 2008. We have this functionality logged in our system and will do our best to have it implemented for the official release.

Thank you for the heads up!

Regards,
Steve
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[LeBear]

Hi Steve,

I love surprises - especially when I know them in advance!  (hint, hint!)

Actually, I'm revisiting my code for the Ajax queue, and it appears I'm already finding a change that I would like to confirm.

I use the onRequestStart and onRequestEnd events of the RadAjaxManager.  I don't believe the onRequestEnd event fired if there was a timeout/non-response from the server before, and now I'm seeing one.

I used to use setTimeout to check for a non-response and handle it accordingly.  Now, the onRequestEnd is firing and I have to check for a non-response differently.

Is this a change made on your end, or am I seeing a change to how Ajax itself works?

I'm changing my code now, but I'd like to know what other surprises I might be in store for.

Thanks.

[Steve]

Hi Barry,

I've already gave out the first new addition - request queuing. We're also considering improved ajax error handling for the AjaxManager :)
As for the ajax request timeout, the approach from this help article is no longer needed as MS AJAX incorporates its own AsyncPostBackTimeout property which cares of this for us.

Regards,
Steve
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center