Re: CAP Last call???

[Bruce_Kahn@xxxxxxxxxxxxxxxx]

Pat wrote on 03/12/2003 12:35:26 PM:
>                    
                     
     All those violently
> opposed please respond to the list with specific reasons why you are
> opposed.  

Another issue from WAAAY back was the
proliferation of top level Response Codes in CAP.  From Section 10.11. Response
Codes:

    Code      
       Description
    --------------------------------------------------------------
    2.0               Success.
The parameters vary with the
                    
 operation and are specified.

    2.0.3             In response
to the client issuing an
                    
 "abort" reply, this reply code indicates
                    
 that any command currently underway was
                    
 successfully aborted.

    3.1.4             Capability
not supported.

    4.1               Calendar
store access denied.

    6.1               Container
not found.

    6.2               Attempt
to create or modify an object
                    
 such that it would overlap another object
                    
 in either of the following two circumstances:

                    
 (a) One of the objects has a TRANSP
                    
 property set to OPAQUE-NOCONFLICT or
                    
 TRANSPARENT-NOCONFLICT.

                    
 (b) The calendar's ALLOW-CONFLICT
                    
 property is set to FALSE.

    6.3               Bad
args.

    6.4               Permission
denied - VCAR restriction.
                    
 A VCAR exists and the CS will not perform
                    
 the operation.

    7.0               A timeout
has occurred. The server was
                    
 unable to complete the operation in the
                    
 requested time.

    8.0               A failure
has occurred in the CS
                    
 that prevents the operation from
                    
 succeeding.

    8.1               A query
was performed and the query is
                    
 too complex for the CS. The operation
                    
 was not performed.

    8.2               Used
to signal that an iCalendar object has
                    
 exceeded the server's size limit

    8.3               A DATETIME
value was too far in the future
                    
 represented on this Calendar.

    8.4               A DATETIME
value was too far in the past
                    
 to be represented on this Calendar.

    8.5               An attempt
was made to create a new
                    
 object but the unique UID specified is
                    
 already in use.

    9.0               An unrecognized
command was received.
                    
 Or an unsupported command was received.


    10.4              The
operation has not been performed
                    
 because it would cause the resources
                    
 (memory, disk, CPU, etc) to exceed the
                    
 allocated quota.

This adds 6, count 'em
6, new top level classes above and beyond the 4 defined in RFC 2445:

     |==============+===============================================|
     | Short Return | Longer Return Status Description  
           |
     | Status Code  |          
                     
              |
     |==============+===============================================|
     |    1.xx      | Preliminary success.
This class of status     |
     |              | of status
code indicates that the request has |
     |              | request
has been initially processed but that |
     |              | completion
is pending.                  
     |
     |==============+===============================================|
     |    2.xx      | Successful. This
class of status code         |
     |              | indicates
that the request was completed      |
     |              | successfuly.
However, the exact status code   |
     |              | can
indicate that a fallback has been taken.  |
     |==============+===============================================|
     |    3.xx      | Client Error.
This class of status code       |
     |              | indicates
that the request was not successful.|
     |              | The
error is the result of either a syntax or |
     |              | a semantic
error in the client formatted      |
     |              | request.
Request should not be retried until  |
     |              | the
condition in the request is corrected.    |
     |==============+===============================================|
     |    4.xx      | Scheduling Error.
This class of status code   |
     |              | indicates
that the request was not successful.|
     |              | Some
sort of error occurred within the        |
     |              | calendaring
and scheduling service, not       |
     |              | directly
related to the request itself.       |
     |==============+===============================================|

Nowhere can I find a description
of these new top level classes and what they mean. (What the hell is a
class 9x. response code good food for and how does it compare with a class
10.x or 8.x???).   

I have previously noted
that there is NO 5.x description or class but that has somehow been overlooked.
 I have also noted that we have a 10.4 but no 10.0, 10.1, 10.2 or
10.3.  Basically we need to take a cleanup pass over the new status
codes to make sure we organzie them properly and cleanly.

We should clearly define
these new top level classes (ala RFC 2445) and possibly consolidate them
down so we have a deeper response tree than a flatter one.  After
all that is why we defined the value to be hierarchical in the first place
in iCalendar.

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