From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: falkdayaram@lavabit.com Newsgroups: gmane.emacs.devel Subject: Unifying network stream Date: Fri, 1 Jul 2011 18:31:55 -0400 (EDT) Message-ID: <64435.199.48.147.39.1309559515.squirrel@lavabit.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1309564766 16983 80.91.229.12 (1 Jul 2011 23:59:26 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Jul 2011 23:59:26 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 02 01:59:22 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QcncH-0002s5-UL for ged-emacs-devel@m.gmane.org; Sat, 02 Jul 2011 01:59:22 +0200 Original-Received: from localhost ([::1]:59721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcncG-0008MA-Bm for ged-emacs-devel@m.gmane.org; Fri, 01 Jul 2011 19:59:20 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcmFj-0007Q7-1K for emacs-devel@gnu.org; Fri, 01 Jul 2011 18:31:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QcmFh-0005IS-NI for emacs-devel@gnu.org; Fri, 01 Jul 2011 18:31:58 -0400 Original-Received: from karen.lavabit.com ([72.249.41.33]:34780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcmFh-0005I8-IG for emacs-devel@gnu.org; Fri, 01 Jul 2011 18:31:57 -0400 Original-Received: from a.earth.lavabit.com (a.earth.lavabit.com [192.168.111.10]) by karen.lavabit.com (Postfix) with ESMTP id CDEE115F546 for ; Fri, 1 Jul 2011 17:31:55 -0500 (CDT) Original-Received: from lavabit.com (199.48.147.39) by lavabit.com with ESMTP id SYU1J9ZNMT4B for ; Fri, 01 Jul 2011 17:31:55 -0500 Original-Received: from 199.48.147.39 (SquirrelMail authenticated user falkdayaram) by lavabit.com with HTTP; Fri, 1 Jul 2011 18:31:55 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=H4FL2H4gG0S6f8KcztvAgJ6DdZyxjWEPo+XmuDXxhngEjC9HLAMcZPtrYDJACIOV52FaL3a+D1ZXjui6kS6MqUAVibZ0TUAo7wgr8PnOYLU1vIFdQaxRgYoeZDdDjABwUrFhWyyKBWKp7DWtyccgbx5GNIkUu1+9kJvcux4ceAs=; h=Message-ID:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; User-Agent: SquirrelMail/1.4.13 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 72.249.41.33 X-Mailman-Approved-At: Fri, 01 Jul 2011 19:51:34 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:141414 Archived-At: I am using GNU Emacs in a corporate environment. Due to inhouse restrictions I am not able to use the inbuilt network stream functions (open-network-stream, starttls-open-stream, open-tls-stream, open-gnutls-stream etc.). To workaround our inhouse proxies and firewalls, I completly rewrote the network stream/tls/starttls implementation to bypass our infrastructure. Whilst emacs provides great tools to implement such a major change, I am still struggeling to keep my patches up with upstream development. Other than that, there are so many different function that may be used to open network streams, implemented in so many different places. It would be great if the creation of networ= k streams is unified in one single function (open-network-stream). I could advice this function then, and would not have to deal with all the other entry points in my code. Is there any chance this could be implemented in emacs 24? I am probably not the only one out here who uses an own network backend.