Determining Acceptable Response Delays

转载 2007年09月15日 15:57:00
JavaTM Look and Feel Design Guidelines: Advanced Topics > Part II: Special Topics > 6: Responsiveness > Determining Acceptable Response Delays   PreviousNextContents/Index/Search


 

Determining Acceptable Response Delays

The term response delay refers to how long an application takes to acknowledge or fulfill a particular user request. Providing responsiveness in an application depends on achieving response delays that are acceptable to users. The longer an application's response delays are, the more time that its users lose when they make errors--especially if those errors are hard to correct. Anxiety about making time-consuming errors can frustrate users, causing them to work more slowly yet make more errors because they lose their concentration.

Inappropriately short response delays can cause problems, too. For example, one such problem occurs if an application displays and erases a message faster than users can read it. If an application displays and erases successive sets of information faster than users can read them or respond to them, users nonetheless try to keep up. As a result, they make more errors, because the application, though fast, does not keep pace with its users.

Some user interface events require shorter response delays than others. For example, an application's response to a user's mouse click or key press needs to be much faster than its response to a request to save a file. Table 13 shows the maximum acceptable response delay for typical interface events.

 

In your application, make each response delay as short as possible, unless users need time to see the displayed information before it is erased. Tools for Measuring Response Delays describes techniques for measuring response delays in your application.

The acceptable response delay for each event is based on a typical user's sense that the event is a logical point at which to stop or pause. The greater that sense is, the more willingly the user will wait for a response.

Verify that your application responds to users' requests within the limits listed in Table 13. If the application cannot respond within those limits, it probably has one or more general problems--ones caused by a particular algorithm or module. To find such problems, analyze the entire application in detail.

For example, one problem might be that your application requires a more powerful computer system than the one on which it was tested. If so, work with your marketing representative to determine the true minimum system requirements for your application.

Verify that your application provides feedback within 100 milliseconds (0.1 second) after each key press, movement of the mouse, or other physical input from the user.

Verify that your application provides feedback within 100 milliseconds (0.1 second) after each change in the state of controls that react to input from the user--for example, displaying menus or indicating drop targets.

Verify that your application takes no longer than 1 second to display each progress indicator, complete each ordinary user command, or complete each background task.

Verify that your application takes no longer than 10 seconds to accept and process all user input to any task--including user input to each step of a multistep task, such as a wizard.


 

Table 13   Maximum Acceptable Response Delays for Typical Events 
User Interface Events Maximum Acceptable Response Delay

Mouse click; pointer movement; window movement or resizing; key press; button press; drawing gesture; other user-input event involving hand-eye coordination

0.1 second (100 milliseconds)

Displaying progress indicators; completing ordinary user commands (for example, closing a dialog box); completing background tasks (for example, reformatting a table)

1.0 second

Displaying a graph or anything else that a typical user would expect to take time (for example, displaying a new list of all a company's financial transactions for an accounting period)

10.0 seconds

Accepting and processing all user input to any task

10.0 seconds


SpringMVC - 406 Not Acceptable异常的可能原因及解决方案

情况一引起的原因: 由于设置了@ResponseBody,要把对象转换成json格式,缺少转换依赖的jar包,故报错。 解决办法: 加入依赖的jar,jackson-core-asl-x.x.x...
  • wuseyukui
  • wuseyukui
  • 2016年12月13日 15:28
  • 2048

改善深层神经网络第一周-Regularization

RegularizationWelcome to the second assignment of this week. Deep Learning models have so much flexi...
  • u011324454
  • u011324454
  • 2017年11月27日 20:14
  • 419

SOCKS代理的实现

网络编程中,对于数据传输实时性要求较高的场合,大家都会选择UDP来作为数据传输协议,在TCP/IP协议族中UDP协议较TCP协议需要的网络系统资源更少。然而在企业应用中,由于网络安全原因等会导致除了特...
  • petershina
  • petershina
  • 2013年06月22日 19:25
  • 1665

使用response对象下载文件

工作中碰到使用Java下载文件的情况,对一些特殊情况纠结了很久,总算解决了,记录下对下载问题的探究过程以及中间碰到的坑。 一、使用response下载 使用response对象的正常下载 r...
  • u010393758
  • u010393758
  • 2017年06月26日 20:06
  • 2491

JavaWeb学习篇之----容器Response详解

今天在来看一下Response容器的相关知识,其实这篇blog早就应该编写了,只是最近有点忙,所以被中断了。下面我们就来看一下Response容器的相关知识吧。Response和我们即将在后面说到的R...
  • jiangwei0910410003
  • jiangwei0910410003
  • 2014年04月03日 18:36
  • 36176

Spark(八) -- 使用Intellij Idea搭建Spark开发环境

Intellij Idea下载地址: 官方下载 选择右下角的Community Edition版本下载安装即可本文中使用的是windows系统 环境为: jdk1.6.0_45 scala2...
  • qq1010885678
  • qq1010885678
  • 2015年05月24日 20:07
  • 9897

Request与Response常用方法总结

Request与Response常用方法总结
  • Konaji
  • Konaji
  • 2016年01月08日 14:18
  • 8241

Laravel框架学习(Response)

1、Response篇 1.1 基本响应最基本的HTTP响应只需在路由闭包或控制器动作中返回一个简单字符串即可,但是具体业务逻辑中大部分响应都是在控制器动作中返回Response实例或者视图。Res...
  • fationyyk
  • fationyyk
  • 2016年03月11日 13:26
  • 5654

response实现验证码

HTML代码: 重定向登陆页面 输入姓名 输入密码 ...
  • u010853261
  • u010853261
  • 2016年01月28日 22:08
  • 457

response常用方法

一、Write方法   Response 对象的Write 方法可以向发往客户端浏览器的HTML 文件中直接输出信息。也就是说,Reponse 对象的Write 方法将信息从 Web 服务器输出...
  • wind8195
  • wind8195
  • 2016年09月18日 12:09
  • 775
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:Determining Acceptable Response Delays
举报原因:
原因补充:

(最多只允许输入30个字)