Re: [ldapext] Request Progress Reporting

[Andrew Findlay <andrew.findlay@skills-1st.co.uk>]

On Thu, Apr 02, 2009 at 08:02:03AM -0700, Howard Chu wrote:

>> The idea currently is to attach a "ProgressReport" control to any request. The
>> control will specify a time interval to indicate how often progress updates
>> should be returned.
>
> I forgot to mention - time intervals should probably be in units smaller 
> than seconds, but probably not smaller than milliseconds. Human factors 
> tells us that most users don't perceive lag until intervals exceed 100ms.

I would suggest that report messages should include some
representation of wallclock time at the server, so that clients can
allow for network latency and jitter when interpreting them. This is a
common strategy when making SNMP queries: a client will usually
request the values of some counters and also the value of the server
agent's "time since boot" counter.

>> ProgressReport updates may be attached in Response controls accompanying
>> Search Response messages, Result messages, and also in Intermediate Response
>> messages.

Clients must understand that an indication of progress is not an
indication that the operation will ever finish, nor that it will be
successful if it does.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext