Bugzilla – Full Text Bug Listing
| Summary: | Vague values in Server Timeout delay | ||
|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | Danny Ju <danny.ju> |
| Component: | wst.server | Assignee: | Angel Vera <arvera> |
| Status: | CLOSED DUPLICATE | QA Contact: | Tim deBoer <deboer> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | deboer, jgarms, rfrost |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
This is an attempt to abstract away the differences in machine and server speed. Each server type has it's own timeout delay, but users said they wanted a way to adjust these for their machine performance without setting a single value for all servers, which might be appropriate for some server types but way too long for others. I think I have a request open somewhere to allow individual timeouts per server; if not I'd like to at least find a way or getting rid of the global setting. Hi Tim. Is there a plan to have this feature in 2.0 "...allow individual timeouts per server..." No, too late for 2.0. Server types can override their defaults to set a better value, but there is no 'default' other than the global ones for local and remote. Assigning to Angel since he'll be working on the timeout settings for 3.0. This can probably be duped to the bug used to make the changes. *** This bug has been marked as a duplicate of bug 121593 *** Closing duplicate. |
Build ID: M20070212-1330 Steps To Reproduce: STEPS_TO_REPRODUCE: Window --> Preferences -->Server Server timeout delay: EXPECTED_BEHAVIOR: a few values (i.e. 5, 10 minutes)and the opportunity for a user to set the value in minutes. ACTUAL_BEHAVIOR: the user has a choice of some vague values: { Longer | Long | Normal | Short Shorter } More information: