Hi All, Thanks for the comments and suggestions. I'm not sure how 'pipelining' works, but I'll look into it. I was already looking at libcurl to see what optimizations were available. Since the present implementation uses only one thread for the download, the libcurl multi-interface might be just the thing.
As Curt reported, my understanding of the OSM usage rules is that we can not have more than two simultaneous download threads. I'll also recheck that understanding. 73, ...jerry KA6HLD On Tue, Jul 27, 2010 at 5:45 PM, Jeremy McDermond <[email protected]> wrote: > > On Jul 27, 2010, at 5:38 PM, James Cameron wrote: > >> On Tue, Jul 27, 2010 at 05:35:11PM -0700, Jeremy McDermond wrote: >>> I haven't looked at the Xastir code, but note that libcurl has a >>> pipelining option that you can turn on so that subsequent calls to the >>> same server will be pipelined. >> >> Yes, that works if you're using libcurl in one thread, but not in new >> threads. If there is a new thread for every tile fetch, then this >> optimisation won't function. > > But I would imagine that if you had two worker threads each with an instance > of the pipelining libcurl handle that they could each pipeline on separate > threads. I could be completely wrong though. > >> >> -- >> James Cameron >> http://quozl.linux.org.au/ > > > -- > Jeremy McDermond (NH6Z) > Xenotropic Systems > [email protected] > > > > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
