From: Mark Plaksin <happy@mcplaksin.org>
Subject: Re: url-cache - (require 'url)
Date: Sun, 15 Jan 2006 21:49:26 -0500 [thread overview]
Message-ID: <874q44x4y1.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: m14q446h9s.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> 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.
next prev parent reply other threads:[~2006-01-16 2:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 17:48 url-cache - (require 'url) David Reitter
2006-01-02 5:08 ` Stefan Monnier
2006-01-02 9:47 ` David Reitter
2006-01-02 16:25 ` Stefan Monnier
2006-01-02 18:03 ` David Reitter
2006-01-03 1:46 ` Stefan Monnier
2006-01-03 9:51 ` David Reitter
2006-01-03 15:54 ` Stefan Monnier
2006-01-03 16:15 ` David Reitter
2006-01-03 20:05 ` Stefan Monnier
2006-01-05 22:11 ` Stefan Monnier
2006-01-06 18:12 ` Mark Plaksin
2006-01-09 1:37 ` Stefan Monnier
2006-01-14 18:32 ` Mark Plaksin
2006-01-15 4:45 ` Stefan Monnier
2006-01-15 4:59 ` Mark Plaksin
2006-01-15 6:09 ` Stefan Monnier
2006-01-15 18:18 ` Mark Plaksin
2006-01-16 2:26 ` Stefan Monnier
2006-01-16 2:49 ` Mark Plaksin [this message]
2006-01-16 18:45 ` Stefan Monnier
2006-02-19 19:56 ` Mark Plaksin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874q44x4y1.fsf@stone.tss.usg.edu \
--to=happy@mcplaksin.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.