Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #71143

Re: Real-world use of concurrent.futures

Show key headers only | View raw

On Fri, May 9, 2014 at 5:45 AM, Marko Rauhamaa <marko@pacujo.net> wrote:
> 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.

Be careful. A naive implementation can open you up to various security
issues. In the case of DNS, source port randomization is important to
the prevention of cache poisoning; if you don't know what I'm talking
about, pick a language/library that does the work for you, rather than
doing everything yourself :)

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

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