From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: more url-utils? Date: Mon, 16 May 2011 23:58:47 +0200 Message-ID: References: <8739kgqbui.fsf@gnu.org> <871uzy7b9o.fsf@lifelogs.com> <877h9q5ub7.fsf@lifelogs.com> <87hb8u4a5x.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1305583138 918 80.91.229.12 (16 May 2011 21:58:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 16 May 2011 21:58:58 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 16 23:58:54 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 1QM5oU-0004KP-5N for ged-emacs-devel@m.gmane.org; Mon, 16 May 2011 23:58:54 +0200 Original-Received: from localhost ([::1]:53249 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM5oT-0007R4-NQ for ged-emacs-devel@m.gmane.org; Mon, 16 May 2011 17:58:53 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:38306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM5oR-0007Qz-7Z for emacs-devel@gnu.org; Mon, 16 May 2011 17:58:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QM5oP-0000EN-V0 for emacs-devel@gnu.org; Mon, 16 May 2011 17:58:51 -0400 Original-Received: from batman.blixtvik.net ([87.96.254.3]:39573) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM5oP-0000E4-Mw for emacs-devel@gnu.org; Mon, 16 May 2011 17:58:49 -0400 Original-Received: from www.verona.se (3-208-96-87.cust.blixtvik.se [87.96.208.3]) by batman.blixtvik.net (Postfix) with ESMTP id B1FF27F96C4; Mon, 16 May 2011 23:58:47 +0200 (CEST) Original-Received: from chopper (unknown [192.168.201.6]) by www.verona.se (Postfix) with ESMTP id A510AA8A181; Mon, 16 May 2011 23:58:47 +0200 (CEST) In-Reply-To: <87hb8u4a5x.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 16 May 2011 16:18:02 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 87.96.254.3 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:139450 Archived-At: Ted Zlatanov writes: > On Mon, 16 May 2011 23:07:49 +0200 joakim@verona.se wrote: > > j> Stefan Monnier writes: >>>>>> After looking at many examples in Emacs, I can't find or think of any >>>>>> need for the headers *as text* in the code I've seen. I would: > SM> That sounds right. >>>> ...so can I go ahead with my proposal or would you rather be >>>> conservative and keep the old behavior, making API users turn off >>>> headers explicitly? >>> >>> There are 3 parts. >>> - removal of header text. >>> - backward compatibility. >>> - providing header info in a non-textual format. >>> >>> All three are important. > > j> Teds proposal addresses all three concerns right? > j> - The new API does what coders expect, no information is lost > j> - the old api is retained but marked obsolete > j> - headers are accessible in alist format > > j> Its more work but Teds volunteered to do it. Great! > > I don't think marking the old API obsolete will preserve backwards > compatibility. But if Stefan thinks so, I'll do it according to my > proposal. Otherwise he'll have to decide what the API will be. > > I don't mind the extra work if it improves Emacs. Right now using > url-*.el to just get some data is pretty painful compared to Perl's LWP, > for instance. True. We had a little inhouse "competition" comparing implementations of reading and parsing an internal REST datasource. My Emacs implementation was pretty lean compared with Android/Iphone implementations, but the Clojure implementation was five lines of code. Perls would be 5 characters I presume :) > > Ted > -- Joakim Verona