[CLOSED] [#428] Globally increase Ajax timeout for DirectMethod calls?

[rthiney]

Is there a way to globally set the Ajax timeout for all DirectMethod calls across entire site?

[geoffrey.mcgill]

I thought we had a Global property for AjaxTimeout, but apparently not. Best I could find for the moment is:

http://forums.ext.net/showthread.php...l=1#post121724

We're going to add .AjaxTimeout as a Global property, which will be available on the ResourceManager, in the Web.config, Session and Application objects.

This new property should be committed to Svn right away.

[geoffrey.mcgill]

Created new Issue to track this property:

https://github.com/extnet/Ext.NET/issues/428

[rthiney]

Created new Issue to track this property:

https://github.com/extnet/Ext.NET/issues/428

Right on, thanks Geoff..will use work around until...

[Daniil]

Done in revision 5645. It will go to the v2.5 release.

ResourceManager

<ext:ResourceManager runat="server" AjaxTimeout="120000" />

Web.config

<extnet ajaxTimeout="120000" />

It is also possible to set up via Application or Session global objects.

Application["Ext.Net.AjaxTimeout"] = 120000;

[michaeld]

Thank you for this suggestion and addition. This will definitely help while debugging. I time-out a lot when I'm stepping through code.

[michaeld]

I would additionally like to request this value be in seconds instead of milliseconds.

[Daniil]

Thank you for the feedback, @michaeld!

[Daniil]

I would additionally like to request this value be in seconds instead of milliseconds.

It makes good sense. It is very unlikely that an AjaxTimeout is going to be less than 1 second.

Well, originally, we followed ExtJS (maybe, a bit blindly). There is milliseconds used for such properties.

Ok, if we change AjaxTimeout to seconds, a developer would expect all Timeout settings to be in seconds. For example,

<ext:AjaxProxy Timeout="30" />

But it is in milliseconds currently. So, there will be inconsistency.

If change an AjaxProxy's Timeout and others to seconds we get a breaking change. Is it worth enough despite introducing such a breaking change? I am not sure.

Again, I agree seconds looks much better for that, but in the current situation I would probably leave milliseconds.

What do you think, Geoffrey?

[ALobpreis]

Hi, Daniil,

In my opinion, perhaps a good option would be to create another property, for example "TimeoutInSeconds", so you avoid creating a breaking change. Of course, both properties would change each other and affect the same internal timeout value.
Another option is to let the current timeout property accept values like "30s".

That's my 2 cents.

Regards,

Andrew