diff options
author | mstenner <mstenner> | 2004-03-15 19:18:19 +0000 |
---|---|---|
committer | mstenner <mstenner> | 2004-03-15 19:18:19 +0000 |
commit | a90a5c944fbf61024415cc02bb1b85b6fb738c07 (patch) | |
tree | e5dc4e05e268a3dbf4c9abf629ea451593921da1 /TODO | |
parent | 4d0c9a5d2e773bcdda2d868847b6791ff5e18bfb (diff) | |
download | urlgrabber-a90a5c944fbf61024415cc02bb1b85b6fb738c07.tar.gz |
updated TODO after alpha-huddle
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 64 |
1 files changed, 37 insertions, 27 deletions
@@ -1,30 +1,40 @@ ALPHA: - * MirrorGroups - get comments from seth/ryan and make any necessary changes - - * Reget - - fix bug with self.opts; the reget code can modify self.opts in the - URLGrabberFileObject, which _may_not_ be a copy of the grabber's - opts. This may go away if we decide to deal with opts a little - differently. - - do a little testing for ftp:// and file:// - - * ponder and implement ryan's idea about restructuring the import style - https://lists.dulug.duke.edu/pipermail/yum-devel/2004-March/000077.html - - * decide on a plan for threading/batch stuff. We don't need to - implement it, but it would be nice to: - - decide if we're going to do it at all (I (mds) lean toward yes) - - decide on an proposed interface - - * make a proper web page describing the features, philosophy, - intended audience, etc. It might be reasonable to promote - urlgrabber from "mini project" to full-fledged project :) - - * in general, decide on some of the questions in the following - sections - not implement, mind you, but at least be able to tell - people what we're planning + * mirror.py + - (mds) make failover more controllable on a per-fetch basis. For + example, be able to control whether the _next index is incremented + at all + + * options + - (both) try and think of better/faster/cleaner ways to handle + grabber options + - (both) think about an interface for setting instance-level + options for an already-created grabber (presumably, mg instances + would support this for their options, too) + + * opener + - (both) try and reduce the number of opener creations - try and + use an instance-level opener for most fetches. + + * threading/batch + - (rt) propose an interface for threaded batch downloads + - (mds) look at making keepalive threadsafe + - (mds) design a new progress-meter interface for threaded + multi-file downloads + - (rt) look at CacheFTPHandler and its implications for batch mode + and byte-ranges/reget + + * reget + - (mds) fix bug with self.opts; the reget code can modify + self.opts in the URLGrabberFileObject, which _may_not_ be a copy + of the grabber's opts. Implementation will depend on what we + decide to do with options. + - (mds) do a little testing for ftp:// and file:// + + * web page + - (mds) make a proper web page describing the features, philosophy, + intended audience, etc. promote urlgrabber from "mini project" to + full-fledged project ALPHA 2: @@ -40,13 +50,13 @@ ALPHA 2: recent chatter on the yum list about Ctrl-C handling. Seth suggests Ctrl-C as a "Skip to Next Mirror" trigger when processing MirrorGroups. + * Make keepalive functionality work when used in multiple threads. + Misc/Maybe: * BatchURLGrabber/BatchMirrorGroup for concurrent downloads and possibly to handle forking into secure/setuid sandbox. - * Make keepalive functionality work when used in multiple threads. - * Consider adding a progress_meter implementation that can be used in concurrent download situations (I have some ideas about this -mds) |