From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark Plaksin Newsgroups: gmane.emacs.devel Subject: Re: url-cache - (require 'url) Date: Sun, 15 Jan 2006 21:49:26 -0500 Message-ID: <874q44x4y1.fsf@stone.tss.usg.edu> References: <87y81zusp7.fsf-monnier+emacs@gnu.org> <87hd8mvc6k.fsf-monnier+emacs@gnu.org> <87ek3qt77f.fsf-monnier+emacs@gnu.org> <21C6AB91-2B23-417B-A0BE-AFD7EA2DA05D@gmail.com> <87irsynxvz.fsf-monnier+emacs@gnu.org> <871wzlp6o1.fsf@stone.tss.usg.edu> <878xtqmbb6.fsf-monnier+emacs@gnu.org> <871wzaoe23.fsf@stone.tss.usg.edu> <87u0c6rtgo.fsf-monnier+emacs@gnu.org> <87bqyexf0q.fsf@stone.tss.usg.edu> <87oe2erpo4.fsf-monnier+emacs@gnu.org> <873bjpxsmd.fsf@stone.tss.usg.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137379822 6012 80.91.229.2 (16 Jan 2006 02:50:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 16 Jan 2006 02:50:22 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 16 03:50:19 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EyKRf-0003TI-Eg for ged-emacs-devel@m.gmane.org; Mon, 16 Jan 2006 03:50:14 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyKTv-0002kU-MA for ged-emacs-devel@m.gmane.org; Sun, 15 Jan 2006 21:52:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EyKTk-0002id-9N for emacs-devel@gnu.org; Sun, 15 Jan 2006 21:52:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EyKTf-0002iD-7S for emacs-devel@gnu.org; Sun, 15 Jan 2006 21:52:19 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyKTa-0002hx-3Y for emacs-devel@gnu.org; Sun, 15 Jan 2006 21:52:11 -0500 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1EyKX0-0006VM-Uy for emacs-devel@gnu.org; Sun, 15 Jan 2006 21:55:43 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EyKRC-0003PS-AY for emacs-devel@gnu.org; Mon, 16 Jan 2006 03:49:42 +0100 Original-Received: from stone.tss.usg.edu ([168.24.82.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Jan 2006 03:49:42 +0100 Original-Received: from happy by stone.tss.usg.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Jan 2006 03:49:42 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 20 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: stone.tss.usg.edu User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.51 (gnu/linux) Cancel-Lock: sha1:a6BdsiCXNEg4tS9VX7v6ZxHq7YE= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:49154 Archived-At: Stefan Monnier writes: >> Maybe there's a better approach to the problem I'm trying to solve. I want >> to add support for ETags to nnrss in Gnus. To do that, nnrss needs access >> to HTTP headers. nnrss currently uses mm-url-insert which calls >> url-insert-file-contents. Those seem like the right functions to use but >> they don't provide access to the HTTP headers. > > Why do they seem better to you than url-retrieve (or even url-http) given > the fact that they do not give you the info you need? Because url-insert-file-contents does some coding-system things that I assume are important for inserting URLs into buffers. I don't know anything about coding-systems. I could write a new function that uses url-retrieve or url-http but I'd probably have to duplicate the coding-system parts which seems wasteful. It also seems that other applications that want to insert the contents of a URL could benefit from having access to HTTP headers.