Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: Re: How many people mark spam in gmane groups?
Date: Tue, 15 Apr 2003 21:42:07 +0000 (UTC)	[thread overview]
Message-ID: <87smsj8mjq.fsf@eris.void.at> (raw)
In-Reply-To: <4nvfxfa746.fsf@lockgroove.bwh.harvard.edu>

Today, Ted Zlatanov <tzz@lifelogs.com> wrote:
> (progn
>   (with-temp-buffer
>     (let ((host "spam.gmane.org")) 
>       (or (setq tcp-connection
> 		(open-network-stream 
> 		 "URL ping"
> 		 (buffer-name)
> 		 host
> 		 80))
> 	(error "Could not open connection to %s" host))
>       (set-marker (process-mark tcp-connection) (point-min))
>       (set-process-filter tcp-connection
>       'net-utils-remove-ctrl-m-filter) (process-send-string
>       tcp-connection
> 			   (format "GET /gmane.emacs.help:8479
> 			   HTTP/1.1\nHost: spam.gmane.org\n\n")))))


> It seems correct to me.  Since the temp-buffer gets killed, that will
> kill the network connection as well, right?

The important question is, will this work if the network connection
gets killed before gmane handles the request? This was what made me use
(asynchronous) url-retrieve, which works pretty much like your
solution above, only (seemingly) more asynchronously. (-:

Maybe somebody with knowledge of php can tell us how this kind of error
gets handled or if it is an error at all?

-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
irc.freenode.net's #emacs - online emacs advice from IRC addicts




  reply	other threads:[~2003-04-15 21:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 15:59 Ted Stern
2003-04-02 16:54 ` Reiner Steib
2003-04-02 20:58   ` Jon Ericson
2003-04-05 13:20   ` Ted Zlatanov
2003-04-05 23:16     ` Reiner Steib
2003-04-07 20:49       ` Ted Zlatanov
2003-04-12 15:50         ` Andreas Fuchs
2003-04-12 20:58           ` Lars Magne Ingebrigtsen
2003-04-13 10:56             ` Andreas Fuchs
2003-04-13 13:31               ` Lars Magne Ingebrigtsen
2003-04-14 19:33               ` Ted Zlatanov
2003-04-14 21:03                 ` Andreas Fuchs
2003-04-14 21:05                 ` Reiner Steib
2003-04-14 23:32                   ` Ted Zlatanov
2003-04-15 14:24                     ` Reiner Steib
2003-04-15  5:34                   ` Steinar Bang
2003-04-15 14:23                     ` Reiner Steib
2003-04-15 19:33                     ` Ted Zlatanov
2003-04-15 21:42                       ` Andreas Fuchs [this message]
2003-04-15 22:31                         ` Lars Magne Ingebrigtsen
2003-04-16  6:02                           ` Andreas Fuchs
2003-04-16 16:33         ` Ted Zlatanov
2003-04-26  1:40           ` Jon Ericson
2003-04-29 17:19             ` Ted Zlatanov
2003-04-29 17:48               ` Jon Ericson
2003-04-29 18:04                 ` Ted Zlatanov
2003-04-29 19:48                   ` Jon Ericson
2003-04-30 18:28                     ` Ted Zlatanov
2003-04-30 21:37                       ` Jon Ericson
2003-05-01 17:34                         ` Ted Zlatanov
2003-04-26  2:49           ` Jon Ericson
2003-04-27  3:41             ` Lars Magne Ingebrigtsen
2003-04-28 18:36               ` Jon Ericson
2003-04-29 17:12                 ` Ted Zlatanov
2003-04-30 18:37                   ` Jon Ericson
2003-04-02 19:32 ` Raja R Harinath
2003-04-13  1:31   ` Daniel Néri

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=87smsj8mjq.fsf@eris.void.at \
    --to=asf@void.at \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).