From f1fdb47bfb023afca50016d8a1f14d506811e83c Mon Sep 17 00:00:00 2001 From: JP Rosevear Date: Thu, 31 Aug 2000 20:41:35 +0000 Subject: Kill off more old, dead files 2000-08-31 JP Rosevear * Kill off more old, dead files svn path=/trunk/; revision=5150 --- libical/design-data/status-new.txt | 56 -------------------- libical/design-data/status.foo | 104 ------------------------------------- 2 files changed, 160 deletions(-) delete mode 100644 libical/design-data/status-new.txt delete mode 100644 libical/design-data/status.foo (limited to 'libical/design-data') diff --git a/libical/design-data/status-new.txt b/libical/design-data/status-new.txt deleted file mode 100644 index 9e7bbf83a7..0000000000 --- a/libical/design-data/status-new.txt +++ /dev/null @@ -1,56 +0,0 @@ -2.0 STATOK Operation was successfully performed. -2.0.1 STARTSENDATA Start ICAL input; end with . -2.0.11 OKDATAFOLLOWS The request was processed successfully. Reply data follows on the next line and terminates with . -2.0.2 REPLYPENDING A timeout has occurred. The server is still working on the reply. Use CONTINUE to continue waiting for the reply or ABORT to terminate the command. -2.0.3 ABORTED The command currently underway was successsfully aborted. -2.0.4 WILLATTEMPT The specified Calendar is not here but an attempt will be made to deliver the request or reply to the Calendar anyway. -2.0.5 TRUSTEDWILLQUEUE The request or reply will be queued and delivered to the target calendar when its iRIP server contacts this server and issues the SWITCH command. -2.0.6 WILLATTEMPT The specified Calendar is not here but an attempt will be made to deliver the request or reply to the Calendar anyway. -2.0.7 QUEUED The message has been queued for delivery. -2.0.8 QUEUEEMPTY There are no more queued messages. -2.1 FALLBACK Success. Fallback taken on one or more property values. -2.2 NOCOMMANDINPROGRESS An ABORT or CONTINUE was received when no command was in progress -2.2 IGPROP Success. Invalid property ignored. -2.3 IGPARAM Success. invalid property parameter ignored. -2.4 IGXPROP Success. Unknown non-standard property ignored. -2.5 IGXPARAM Success. Unknown non standard property value ignored. -2.6 IGCOMP Success. Invalid calendar component ignored. -2.7 FORWARD Success. Request forwarded to Calendar User. -2.8 ONEEVENT Success. Repeating event ignored. Scheduled as a single component. -2.9 TRUNC Success. Truncated end date time to date boundary. -2.10 ONETODO Success. Repeating VTODO ignored. Scheduled as a single VTODO. -2.11 TRUNCRRULE Success. Unbounded RRULE clipped at some finite number of instances -3.0 INVPROPNAME Invalid property name. -3.1 INVPROPVAL Invalid property value. -3.2 INVPARAM Invalid property parameter. -3.3 INVPARAMVAL Invalid property parameter value. -3.4 INVCOMP Invalid calendar component sequence. -3.5 INVTIME Invalid date or time. -3.6 INVRULE Invalid rule. -3.7 INVCU Invalid Calendar User. -3.8 NOAUTH No authority. -3.9 BADVERSION Unsupported version. -3.10 TOOBIG Request entity too large. -3.11 MISSREQCOMP Required component or property missing. -3.12 UNKCOMP Unknown component or property found. -3.13 BADCOMP Unsupported component or property found -3.14 NOCAP Unsupported capability. -4.0 BUSY Event conflict. Date/time is busy. -5.0 MAYBE Request MAY supported. -5.1 UNAVAIL Service unavailable. -5.2 NOSERVICE Invalid calendar service. -5.3 NOSCHED No scheduling support for user. -6.1 AUTHENTICATEFAILURE Unsupported authentication mechanism, credentials rejected -6.2 AUTHENTICATIONABORTED Sender aborted authentication, authentication exchange cancelled -8.0 GENERALFAILURE A failure has occurred in the Receiver that prevents the operation from succeeding. -8.1 SERVERTOOBUSY The iRIP Receiver is too busy. -8.2 ICALOBJECTTOOBIG Object has exceeded the server's size limit. -8.3 DATETOOLARGE A DATETIME value was too far in the future to be represented on this Calendar. -8.4 DATETOOSMALL A DATETIME value was too far in the past to be represented on this Calendar. -9.0 INVALIDIRIPCOMMAND An unrecongnized command was received. -9.1 UNEXPECTEDCOMMAND The command is not allowed for the server's current state. -10.1 REFERRAL Accompanied by an alternate address. -10.2 SERVERSHUTDOWN The server is shutting down. -10.3 SERVERSTOPPING FLOOD 2 -10.4 EXCEEDEDQUOTAS The operation would cause a resource to exceed the allocated quota -10.5 QUEUEDTOOLONG The ITIP message has been queued too long. Delivery has been aborted. diff --git a/libical/design-data/status.foo b/libical/design-data/status.foo deleted file mode 100644 index a2591bd26a..0000000000 --- a/libical/design-data/status.foo +++ /dev/null @@ -1,104 +0,0 @@ -2.0 STATOK Operation was successfully performed. - -2.0.1 START-SENDATA Start ICAL input; end with - . - -2.0.11 OK-DATAFOLLOWS The request was processed - successfully. Reply data follows on - the next line and terminates with - . - -2.0.2 REPLY-PENDING A timeout has occurred. The server is - still working on the reply. Use - CONTINUE to continue waiting for the - reply or ABORT to terminate the - command. - -2.0.3 ABORTED In response to the client issuing an - ABORT command, this reply code - indicates that any command currently - underway was successsfully aborted. - -2.0.4 WILL-ATTEMPT The specified Calendar is not here - but an attempt will be made to deliver - the request or reply to the Calendar - anyway. There is a trust relationship - between this iRIP server and the - iRIP server for the target calendar. - -2.0.5 TRUSTED-WILL-QUEUE The specified Calendar cannot be - contacted directly and a trust - relationship exists between this - server and the server on which the - Calendar exists. The request or reply - will be queued and delivered to the - target calendar when its iRIP server - contacts this server and issues the - SWITCH command. - -2.0.6 WILL-ATTEMPT The specified Calendar is not here - but an attempt will be made to deliver - the request or reply to the Calendar - anyway. There is not a trust - relationship between the iRIP server - and the iRIP server for the target - calendar. - -2.0.7 QUEUED The message has been queued for - delivery. - -2.0.8 QUEUE-EMPTY There are no more queued messages. - -2.2 NO COMMAND IN PROGRESS An ABORT or CONTINUE was received when - no command was in progress - -6.1 AUTHENTICATE FAILURE Unsupported authentication mechanism, - credentials rejected - -6.2 AUTHENTICATION ABORTED Sender aborted authentication, - authentication exchange cancelled - -8.0 GENERAL FAILURE A failure has occurred in the Receiver - that prevents the operation from - succeeding. - -8.1 SERVER TOO BUSY Sent when a session cannot be - established because the iRIP - Receiver is too busy. - -8.2 ICAL OBJECT TOO BIG Used to signal that an ICAL object has - exceeded the server's size limit. - -8.3 DATE TOO LARGE A DATETIME value was too far in the - future to be represented on this - Calendar. - -8.4 DATE TOO SMALL A DATETIME value was too far in the - past to be represented on this - Calendar. - -9.0 INVALID iRIP COMMAND An unrecongnized command was received. - -9.1 UNEXPECTED COMMAND A command was issued in a manner - inconsistent with the state diagram. - For example, issuing the SENDATA - command without having specified any - RECIPIENTs will cause this error. -10.1 REFERRAL Accompanied by an alternate address. - The RECIPIENT specified should be - contacted at the given alternate - address. The referral address MUST - follow the reply code. - -10.2 SERVER SHUT DOWN The server is shutting down. - -10.3 SERVER STOPPING FLOOD 2 - - -10.4 EXCEEDED QUOTAS The operation has not be performed - because it would cause the resources - (memory, disk, CPU, etc) to exceed the - allocated quota - -10.5 QUEUED TOO LONG The ITIP message has been queued too - long. Delivery has been aborted. \ No newline at end of file -- cgit