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 20:57:11 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87boyzcv0o.fsf@lifelogs.com> References: <87fwogaxzb.fsf@stupidchicken.com> <87mxilezg8.fsf@lifelogs.com> <87boz0eov8.fsf@lifelogs.com> <87mxikrulm.fsf@lifelogs.com> <871uzw5asv.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1305770261 21903 80.91.229.12 (19 May 2011 01:57:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 19 May 2011 01:57:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 19 03:57:34 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 1QMsUX-0002F9-VI for ged-emacs-devel@m.gmane.org; Thu, 19 May 2011 03:57:34 +0200 Original-Received: from localhost ([::1]:45687 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMsUX-0007gH-G5 for ged-emacs-devel@m.gmane.org; Wed, 18 May 2011 21:57:33 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:54523) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMsUV-0007gA-3E for emacs-devel@gnu.org; Wed, 18 May 2011 21:57:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMsUT-0005RQ-WC for emacs-devel@gnu.org; Wed, 18 May 2011 21:57:31 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:34436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMsUT-0005R9-K4 for emacs-devel@gnu.org; Wed, 18 May 2011 21:57:29 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QMsUO-0002BU-J2 for emacs-devel@gnu.org; Thu, 19 May 2011 03:57:24 +0200 Original-Received: from c-67-186-102-106.hsd1.il.comcast.net ([67.186.102.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 May 2011 03:57:24 +0200 Original-Received: from tzz by c-67-186-102-106.hsd1.il.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 May 2011 03:57:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 58 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-67-186-102-106.hsd1.il.comcast.net 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:BazwEUpZ95F76rYSU0PZHAk/Zvs= 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:139496 Archived-At: On Wed, 18 May 2011 19:05:57 -0300 Stefan Monnier wrote: SM> But your `body' is nothing more than the body of the callback if SM> passed as a lambda (and indeed within the macro you'll have to wrap SM> `body' with a `lambda' to use it in the process-sentinel), so SM> providing both `callback' and `body' arguments is not very useful. I thought it was more readable to cradle statements in a "with-xyz" macro (e.g. `with-temp-file', `with-parsed-tramp-file-name') than to craft a lambda for a callback. It's not a big deal, I can write the macro on top of `url-fetch' anyhow. >> (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) >> ...) SM> I'm not sure all those args make sense, but yes, that sounds SM> about right. We should think hard about what those args should be, SM> within the larger context of URL rather than only http. Yeah. So perhaps we simply write `url-http-fetch' that specifies the base `url-fetch' props and then adds its own list on top. SM> No, callback just makes it possible to do the request asynchronously, SM> but it can still be performed synchronously and for some URLs we may not SM> know how to perform them asynchronously (as the docstring of SM> url-retrieve already explains). OK. >> 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 SM> ^^^^^^^^^ SM> called >> returns whatever CALLBACK returned. SM> That's a good idea. Kind of like a future. All right, I'll provide that. Are you OK with the defun* approach and having each `url-{http,ftp,etc}-fetch' function build on the base `url-fetch'? Also I think the callback should get the status and then &rest plist. The plist will depend on the URL protocol but there will be common keys to determine the protocol, if there were headers, etc. That's a little bit less functional but the data will not be hidden in buffer-local variables like it is now (although those will still be available). There will be a lot more function parameters on the stack, though--I don't know if that's a problem. Ted