Handling IRC continuation message lines
draft-burri-irc-continuation-message-lines-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Christian Burri | ||
Last updated | 2001-08-08 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Due to the way the IRC protocol is implemented, it may occur that a server sends incomplete messages to a client, so called continuation message lines. There seems to exist confusion about how to handle continuation message lines; many implementations are broken and do not respect them at all. Others rely on timers to complete continuation lines, which is not recommended due to the asyncronous nature of IRC communications. This Memo proposes an algorithm to handle continuation lines received from an IRC connection in such way that no timers are needed, and is intended as a supplement to the existing RFC 1459 which describes the Internet Relay Chat protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)