Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Marko Rauhamaa <marko@pacujo.net>
Newsgroups: comp.lang.python
Subject: Re: Real-world use of concurrent.futures
Date: Thu, 08 May 2014 22:45:03 +0300
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <87tx90t5q8.fsf@elektro.pacujo.net>
References: <536BD338.4070004@andros.org.uk> <mailman.9791.1399576024.18130.python-list@python.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx05.eternal-september.org; posting-host="ff5cf27ef3d5b31f034d3b72bdc27a41"; logging-data="31155"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/OO7X2fXO+uzQfC1yuEkAA"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Cancel-Lock: sha1:584Pqlqdqsa3XquWlM/Mt3HC3XM= sha1:CAFZmIU1l6QW9EaKn/lknhdRYqc=
Xref: csiph.com comp.lang.python:71124

Chris Angelico <rosuav@gmail.com>:

> Before you go too far down roads that are starting to look
> problematic: A DNS lookup is a UDP packet out and a UDP packet in
> (ignoring the possibility of TCP queries, which you probably won't be
> doing here). Maybe it would be easier to implement it as asynchronous
> networking? I don't know that Python makes it easy for you to
> construct DNS requests and parse DNS responses;

That's what I ended up doing when I wrote my home SMTP server.

It's more tedious than difficult. You don't need to have a ready-made
module for everything. An RFC and two hands take you far.


Marko