Bug #754

timeout-issue / hardcoded _dev environment

Added by Peter Niederlag about 11 years ago. Updated almost 9 years ago.

Status:
Accepted
Priority:
Could have
Category:
Backend
Start date:
2008-06-09
Due date:
% Done:

0%

Estimated time:
0.00 h

Description

AOPBrowser doesn't give any feedback to user-input if ajax-requests timeout.

Resources/Public/F3_AOPBrowser_GUI.html has a hardcoded reference to the development-environment (index_dev.php). However development environment doesn't do any caching by default and actions might take (very! > 30s.) long. I found AOPBrowser to be usable only when changing 'index_dev.php' to 'index.php', since otherwise the requested actions seem to have run into an timeout.

Don't know if this is a bug or a feature, at least it would be very nice to give some feedback to the user if the request/action has timed out.

problem-timeout.diff View (618 Bytes) Peter Niederlag, 2008-06-09 14:44

History

#1 Updated by Michael Feinbier about 11 years ago

  • Status changed from New to Accepted

Thanks!
I'll have a look at it :)

Also available in: Atom PDF