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

[Bruce_Kahn@xxxxxxxxxxxxxxxx]

Andrea noted on 01/24/2003 12:03:39 PM:
> For that matter, since we're using BEEP, it can simply close the
> channel and open a new one, no need to drop the session.

Sure thats just as valid.  

It does however have the undesirable
side effect of keeping the unwanted, unbounded, uncontrollable command
going since the CUA is still connected.  (And the CS may refuse to
drop the erant BEEP channel if there is an active command on it or at least
it should if I grok BEEP prose well enough...)

I would expect that a good CS would
take steps to make sure to detect CUA disconnect and deal with it like
aborting in progress commands, doing session related cleanup, etc.  Having
the CUA create a new channel though would NOT cause the same to happen
so the unbounded command would continue its rampage...

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...