From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: more url-utils? Date: Wed, 18 May 2011 09:43:28 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <871uzw5asv.fsf@lifelogs.com> References: <87fwogaxzb.fsf@stupidchicken.com> <87mxilezg8.fsf@lifelogs.com> <87boz0eov8.fsf@lifelogs.com> <87mxikrulm.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1305729844 22414 80.91.229.12 (18 May 2011 14:44:04 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 18 May 2011 14:44:04 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 18 16:43:57 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 1QMhye-0004Yf-Jp for ged-emacs-devel@m.gmane.org; Wed, 18 May 2011 16:43:56 +0200 Original-Received: from localhost ([::1]:42369 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMhye-0005g4-5m for ged-emacs-devel@m.gmane.org; Wed, 18 May 2011 10:43:56 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:51278) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMhya-0005fb-SJ for emacs-devel@gnu.org; Wed, 18 May 2011 10:43:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMhyZ-0007WZ-Fe for emacs-devel@gnu.org; Wed, 18 May 2011 10:43:52 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:48737) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMhyZ-0007WT-5t for emacs-devel@gnu.org; Wed, 18 May 2011 10:43:51 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QMhyW-0004Va-Vv for emacs-devel@gnu.org; Wed, 18 May 2011 16:43:48 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2011 16:43:48 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2011 16:43:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 52 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:6ZyYC/wBbIcyR4ITrpBBuTRLT+8= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:139490 Archived-At: On Wed, 18 May 2011 11:09:25 -0300 Stefan Monnier wrote: SM> What's the difference between the code run in call-back-closure from SM> the code in `body'? >> The body is easier to write explicitly but the callback-closure offers >> more flexibility and backwards compatibility. They are more or less the >> same otherwise (see below for the pseudocode), it's just different types >> of syntactic sugar for different situations. I think the majority of >> uses will be in the synchronous mode, where `with-url-contents-buffer' >> is very convenient. SM> I think you're just afraid of lambda ;-0 ...or are you afraid of macros? ;) SM> Here's my proposal: SM> (defun url-fetch (url &optional silent callback) SM> "Fetch URL into current buffer. SM> If CALLBACK is nil, do it synchronously and return a status flag." OK. The status flag should be nil on failure and t on success. Let's not tie the `url-fetch' status flag to the HTTP status. SM> But I also like the idea of passing url-request-method and such as SM> explicit arguments. (defun* url-fetch (url &rest spec &key silent callback request-data request-method request-extra-headers standalone-mode gateway-unplugged honor-stylesheets confirmation-func cookie-multiple-line cookie-storage cookie-confirmation cookie-secure-storage cookie-secure-confirmation &allow-other-keys) ...) This has less compile-time parameter validation but is much more flexible long-term. SM> And I'm not sure what it should return if CALLBACK is non-nil (both SM> in the case where the request is performed asynchronously and when SM> it's performed synchronously). By the docstring you gave, if CALLBACK is non-nil, it must be asynchronous. So CALLBACK can't be used synchronously. In the asynchronous mode we could return a lambda (see that? I used a lambda!) that can be evaluated to wait until CALLBACK completes and then returns whatever CALLBACK returned. Ted