Author: dylan Date: 2005-03-22 00:48:04 -0500 (Tue, 22 Mar 2005) New Revision: 650
Modified: trunk/ trunk/docs/spec/Haver/Spec.pod Log: [EMAIL PROTECTED]: dylan | 2005-03-20 02:48:04 -0500 foobar. Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk:11166 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk-merge-10131:11178 27e50396-46e3-0310-8b22-ae223a1f35ce:/local:212 e9404bb1-7af0-0310-a7ff-e22194cd388b:/haver/local:851 edfcd8bd-4ce7-0310-a97e-bb1efd40edf3:/local:238 + 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk:11166 1f59643a-e6e5-0310-bc24-f7d4c744f460:/haver/local/trunk-merge-10131:11178 27e50396-46e3-0310-8b22-ae223a1f35ce:/local:212 e9404bb1-7af0-0310-a7ff-e22194cd388b:/haver/local:855 edfcd8bd-4ce7-0310-a97e-bb1efd40edf3:/local:238 Modified: trunk/docs/spec/Haver/Spec.pod =================================================================== --- trunk/docs/spec/Haver/Spec.pod 2005-03-20 07:04:30 UTC (rev 649) +++ trunk/docs/spec/Haver/Spec.pod 2005-03-22 05:48:04 UTC (rev 650) @@ -30,9 +30,9 @@ While chocolate's main purpose is to delight with its delicious taste, haver servers do not have any taste. -Instead, haver servers route messages (events) to their clients, +Instead, haver servers route messages to their clients, and maintain data about their clients and channels. -Monolithic servers will do more than just this, and will handle many events +Monolithic servers will do more than just this, and will handle many messages internally. Micro-servers will offload this burden unto special service clients. =head2 Clients @@ -42,7 +42,7 @@ The vast majority of clients will be users, which are representations of either real people, bots, or GreenReaper. -Services may add new protocol events to the server, +Services may add new protocol messages to the server, produce virtual user-like entities called Agents to interact with the real users, and extend virtual channels into the server allows different forms of server linking. @@ -72,13 +72,13 @@ The haver protocol is in the UTF-8 encoding, as defined in RFC 2279. However, only the first 127 character codes (the ASCII range) -are used for events, identifiers, and delimiters. +are used for message names, identifiers, and delimiters. The protocol is delimited into lines separated by CR LF (0x0D 0x0A). Each line is further delimited by the Tab character (0x09) into a series of tokens. -The first of the tokens is called the command, -the remaining tokens (if any) are refered to as the arguments. +The first of the tokens is called the command or message name. +The remaining tokens (if any) are refered to as the arguments. If a literal tab, carriage return, or line feed needs to be sent, it must be written in escaped form with the Esc character (0x1b). @@ -96,7 +96,7 @@ This section describes formats used in the haver protocol, such as how dates, times, and time zones are formatted. It also describes the format for identifiers (the ids of channels, users, etc), -and events. +and message names. =head2 Dates and Times @@ -127,19 +127,11 @@ Further, the length of the ID must be greater than two and less than or equal to 20 (C<length(id) E<gt> 2 && length(id) <= 20>). -=head2 Events +=head2 Message names -Events must only contain upper-case letters, hyphers, underscores, +Message names must only contain upper-case letters, hyphers, underscores, and colons. (C</[A-Z:_-]/>). -=head1 SERVER EVENTS +=head1 CLIENT MESSAGES -=head2 HAVER(I<server>) -WRITEME - -=head1 CLIENT EVENTS - -=head2 HAVER(I<client>) - -WRITEME
