Re: Getting updates and restarting a long running url request.

References	<CALyJZZXX4cBtx_VVFpEWB8WEkVPNbgj0r-T1XX5nttmZWkNHDw@mail.gmail.com> <CANy1k1jsR3V6muT5HuVRoYMv49MvCRiQCKrmV7c4x2UtrxUJMg@mail.gmail.com> <CALyJZZWAHMqHdV95r1K3x17g9PUze71SRECMBBMWqsD8R1oxFw@mail.gmail.com>
Date	2013-12-26 17:15 -0700
Subject	Re: Getting updates and restarting a long running url request.
From	Jason Friedman <jsf80238@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.4641.1388103358.18130.python-list@python.org> (permalink)

Show all headers | View raw

> Would this not keep requesting/submitting additional (duplicate) BLAST
> queries?
>>
>>  try:
>>             this_result = get_BLAST(id)
>>             result_dict[id] = True
>

I assumed that
NCBIWWW.qblast
waits for a response from the server.

Are you saying that instead it queues a request, and the
NCBIXML.read(blast_result)

command fetches the result?

>
> That said after some more research I found this tread.
> http://lists.open-bio.org/pipermail/biopython/2013-April/008507.html

I read that post to say that you will be submitting one request for a
lot of data points that you will then need to parse, is that true?

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

Thread

Re: Getting updates and restarting a long running url request. Jason Friedman <jsf80238@gmail.com> - 2013-12-26 17:15 -0700

csiph-web