Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #71124
| From | Marko Rauhamaa <marko@pacujo.net> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Real-world use of concurrent.futures |
| Date | 2014-05-08 22:45 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <87tx90t5q8.fsf@elektro.pacujo.net> (permalink) |
| References | <536BD338.4070004@andros.org.uk> <mailman.9791.1399576024.18130.python-list@python.org> |
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
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Real-world use of concurrent.futures Chris Angelico <rosuav@gmail.com> - 2014-05-09 05:06 +1000
Re: Real-world use of concurrent.futures Marko Rauhamaa <marko@pacujo.net> - 2014-05-08 22:45 +0300
Re: Real-world use of concurrent.futures Chris Angelico <rosuav@gmail.com> - 2014-05-09 11:12 +1000
csiph-web