MvCALL timeouts?

[Kent Multer]

Hi folks --

Can someone please refresh my memory on the current state of timeout handling for MvCALLs? As I recall, they finally got it working ... I've just had a client request a custom-module function that involves making an HTTP request, but timing out after 10-12 seconds to return an error message. Is there a way to change the timeout for a single MvCALL, while retaining the normal timeout for all the others?

Thanks --

[aGorilla]

You can change it, but only to a shorter time. I _believe_ the intent is to allow your script to have enough time to report the error, instead of just failing without any explanation.

[Kent Multer]

That would work for me. How do I change the timeout?

Thanks -- Kent

[aGorilla]

From release notes:

'MvCALL takes a new attribute "TIMEOUT". This value is used if it
is smaller than the configured MvCONFIG_CALL_TIMEOUT value.'

I'm going to assume it's as simple as adding TIMEOUT="10" (or whatever value you want) to your MvCALL tag.

Edit: FYI: this was added in 5.03, so won't work with older Empressa engines.