Handling IRC continuation message lines
draft-burri-irc-continuation-message-lines-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2001-08-08 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-burri-irc-continuation-message-lines-00.txt
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
Christian Burri (christian.burri@synecta.ch)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)