Re: CAP 10: 10.1. CAP Commands (CMD) (ABORT/CONTINUE)

[Bruce_Kahn@xxxxxxxxxxxxxxxx]

Doug replied on 01/22/2003 10:54:22 PM:
> I seem to recall objections that all CS's must support bounded
> latency. When we merged iRIP and CAP we agreed that we would
> add bounded latency to CAP and not make it required. A palm
> pilot for example I do not think can do bounded latency.
> 
> Do we need a new CAPABILITY?  SUPPORTS-LATENCY / boolean ?

Ill have to do some searching to check
on that (Vacation induced relaxation is not totally worn off yet).  

If a CUA does not support latency then
just how would it be able to control/stop a command it issued?  That
is, if the Palm CUA sent a search that was taking a long time (a very busy
and impatient exec) and the CU wanted to stop the action then just how
would the CU/CUA be able to do that if they didnt support at least ABORT?
 (Clearly CONTINUE is irrelvant to this discussion).  The only
way if ABORT is not supported by all implementations is to disconnect from
the CS and then reconnect back...  Ack!

Bruce
===========================================================================
Bruce Kahn                  
             INet: Bruce_Kahn@xxxxxxxxxxxxxxxx
Messaging & Collaboration            
    Phone: 978.399.6496
IBM Software Group                
        FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...