I know I should be satisfied with your previous response about trying to put this task to a release in the near futer, and hope this reminder don't bump me back to the end of the backlog I still appreciate the previous response, so don't get me wrong. While I don't know to what extent I can influence priority, I thought I'd give some context to my repeated reminder/request. My assumption is that the secret to unlimited resources is still elusive... I just thought I'd add these details if it can make a difference between 100.3 and 100.4
Our customers work with emergency dispatch, where seconds can help save a life, or keep a fire from spreading out of control. What most people consider a sexy animation, can serve as an added stressor for the operator trying to shave off seconds in their work. In the past, we used WPF runtime for these customers, which allowed to set Zoom and Pan duration. We got a request to reduce the default animation, and ended up at 150ms. This was still considered way to slow, and we ended up turning this off, and the customer was very pleased Whenever we upgrade them to the latest runtime, this missing feature is guaranteed to raise eyebrows and stress levels. I was just reminded of this case today, where one customer is tweaking ArcGIS Server to reduce response times, so I thought I'd provide the information. I don't know how many other API customers work in this field, but if there are, there are sure to be other interested parties besides me