all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mirek Kaim <mirek.kaim@outlook.com>
To: David Edmondson <dme@dme.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [PATCH v1] Fix errors generated when multiple IRC clients talk to a single IRC proxy.
Date: Wed, 15 Oct 2014 17:50:24 +0200	[thread overview]
Message-ID: <COL131-W95D9F8028049B89B3D04C084AA0@phx.gbl> (raw)
In-Reply-To: <cuna9551qle.fsf@gargravarr.hh.sledj.net>

i didn't take a look at erc source yet, but if that is the case, then it's a proof of terribly, and i mean TERRIBLY, bad design. irc 
protocol by its very definition is asynchronous and whatever gets 
received, should be processed regardless of the sender of the command 
that caused the response to be received.

i'm using erc and i'm moderately happy with it, but knowing how it was written, i guess when the time comes that i'll have some spare time, instead of writing patches for it, i'll just code my own irc client for emacs. how can an irc client be working like this is beyond me, it's like it was written without reading rfcs at all.


unic0rn


----------------------------------------
> If multiple IRC clients are connected to a single IRC proxy, an
> instance of erc can receive the response to a NAMES request issued by
> another client. Given that this instance of erc didn't initiate the
> NAMES request, `erc-channel-begin-receiving-names' will not have been
> called and `erc-channel-new-member-names' will be nil. 		 	   		  


      parent reply	other threads:[~2014-10-15 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 14:03 [PATCH v1] Fix errors generated when multiple IRC clients talk to a single IRC proxy David Edmondson
2014-10-15  6:58 ` Thien-Thi Nguyen
2014-10-15  7:06   ` Thien-Thi Nguyen
2014-10-15  7:58   ` David Edmondson
2014-10-15 13:54   ` Stefan Monnier
2014-10-15 15:50 ` Mirek Kaim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=COL131-W95D9F8028049B89B3D04C084AA0@phx.gbl \
    --to=mirek.kaim@outlook.com \
    --cc=dme@dme.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.