[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Weechat-dev] [task #6583] handle netsplits in some better way.

From: anonymous
Subject: [Weechat-dev] [task #6583] handle netsplits in some better way.
Date: Sun, 04 Mar 2007 17:10:14 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070126 Firefox/1.5


                 Summary: handle netsplits in some better way.
                 Project: Wee Enhanced Environment for Chat
            Submitted by: None
            Submitted on: Воскресенье 04.03.2007 at 17:10 UTC
                Category: None
         Should Start On: Воскресенье 04.03.2007 at 00:00 UTC
   Should be Finished on: Пятница 01.01.2038 at 00:00 UTC
                Priority: 1 - Later
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
         Originator Name: darkk
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any



Will be nice if we see something better than 100 lines of nicks with same
quit message, something like
 <-- netsplit (irc.foo.bar irc.42.baz): Nick, Name, Nickname
 --> netsplit over.... (nicklist)

quote from rfc2813

   When "netsplit" (See Section 4.1.6) occur, the "Quit Message" is
   composed of the names of two servers involved, separated by a space.
   The first name is that of the server which is still connected and the
   second name is either that of the server which has become
   disconnected or that of the server to which the leaving client was

      <Quit Message> =  ":" servername SPACE servername

   Because the "Quit Message" has a special meaning for "netsplits",
   servers SHOULD NOT allow a client to use a <Quit Message> in the
   format described above.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]