[3403] in BarnOwl Developers

home help back first fref pref prev next nref lref last post

[barnowl/barnowl] c2866e: Split irc messages into chunks

daemon@ATHENA.MIT.EDU (GitHub)
Mon May 13 20:46:12 2013

Date: Mon, 13 May 2013 17:46:07 -0700
From: GitHub <noreply@github.com>
Reply-To: GitHub <noreply@github.com>
To: barnowl-dev@mit.edu

----==_mimepart_5191894f95fb4_12881329dd41435ed
Date: Mon, 13 May 2013 17:46:07 -0700
Mime-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: <5191894f9790f_12881329dd41436e2@hookshot-fe3-pe1-prd.aws.github.net.mail>

  Branch: refs/heads/master
  Home:   https://github.com/barnowl/barnowl
  Commit: c2866ecce166474ab92c7f75d53d7de0d6d884a0
      https://github.com/barnowl/barnowl/commit/c2866ecce166474ab92c7f75d53d7de0d6d884a0
  Author: Jason Gross <jgross@mit.edu>
  Date:   2013-05-13 (Mon, 13 May 2013)

  Changed paths:
    M perl/modules/IRC/lib/BarnOwl/Module/IRC.pm

  Log Message:
  -----------
  Split irc messages into chunks

From Zephyr:
   barnowl / irc-cutoff / kchen  2013-05-09 16:38  (Everyone Left Wheel Thru)
       This might be an IRC limitation.  RFC 1459 says:
  "IRC messages are always lines of characters terminated with a CR-LF
       (Carriage Return - Line Feed) pair, and these messages shall not
       exceed 512 characters in length, counting all characters including
       the trailing CR-LF. Thus, there are 510 characters maximum allowed
       for the command and its parameters.  There is no provision for
       continuation message lines.  See section 7 for more details about
       current implementations."
  (I didn't read the rest of the RFC to know how many other bytes are
       involved in sending a message.)

I chose 450 to be the default cut-off semi-arbitrarily; freenode seems
to allow up to about 463 characters (to channel #agda, with username
jgross).




----==_mimepart_5191894f95fb4_12881329dd41435ed--

home help back first fref pref prev next nref lref last post