/[axel]/trunk/ROADMAP
ViewVC logotype

Diff of /trunk/ROADMAP

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 54 by phihag-guest, Mon Oct 13 17:03:32 2008 UTC revision 55 by phihag-guest, Tue Oct 14 12:53:43 2008 UTC
# Line 2  Roadmap for Axel v3 Line 2  Roadmap for Axel v3
2  ===================  ===================
3    
4  Note: This document provides only a rough overview what to do next. Refer to the bugtracker ( https://alioth.debian.org/tracker/?group_id=100070&atid=413085 ) for detailled information.  Note: This document provides only a rough overview what to do next. Refer to the bugtracker ( https://alioth.debian.org/tracker/?group_id=100070&atid=413085 ) for detailled information.
5    Pre-release version numbers of Axel 3 will start with 2.99. Starting with the 3.x series, the following version scheme will be adopted:
6    
7    x.y.z
8    
9    x: Complete overhaul of the code structure
10    y: New features and/or speed/size improvements
11    z: Bug fixed
12    
13  Features  Features
14  ========  ========
# Line 69  Check spaces in FTP and HTTP URLs Line 76  Check spaces in FTP and HTTP URLs
76  * Cookies (#310835)  * Cookies (#310835)
77   Can be implemented via -H. The bug called for reading the Netcape-style cookies.txt (Wget's --load--cokies option). Domain-specific cookies could be rather complex to implement. If the implementation of this feature costs more than 100B, it should be deselectable.   Can be implemented via -H. The bug called for reading the Netcape-style cookies.txt (Wget's --load--cokies option). Domain-specific cookies could be rather complex to implement. If the implementation of this feature costs more than 100B, it should be deselectable.
78  * Rate-limit status messages (#TODO)  * Rate-limit status messages (#TODO)
79    * Don't discard first HTTP connection, but use it adaptively (start requests from the end, RST as soon as first task is fullfilled)
80    * A -1 option: Just make one request, and only one.
81    * IPv6 support
82    
83    3.2
84    ===
85    
86    * Write a macro ERROR_MESSAGE(msg) (msg), enclose all _("some long error message") and offer a compilation option for a single error message, see if that yields any size improvements
87    * Check compilation with dietlibc(http://www.fefe.de/dietlibc/) and uclibc(http://www.uclibc.org/):
88            · How to compile with these libraries
89            · Does this actually improve the binary size?
90            · Check warnings/suggestions
91    * valgrind and friends
92    * Test very large -n values. Check pthread thread stack size.
93    
94  Future/Ideas  Future/Ideas
95  ============  ============
96    
 * IPv6 support  
97  * Real FTPS (AUTH)?  * Real FTPS (AUTH)?
98  * Allow downloading to /dev/null for debugging or speed test purposes  * Allow downloading to /dev/null for debugging or speed test purposes (Statefile in memory or so)
99  * Desktop integration, look who likes download accelerators  * Desktop integration, look who likes download accelerators
 * Test very large -n values. Check pthread thread stack size.  
100  * Check the syscalls we make. Check whether timing and read() calls can be optimized  * Check the syscalls we make. Check whether timing and read() calls can be optimized
 * Write a macro ERROR_MESSAGE(msg) (msg), enclose all _("some long error message") and offer a compilation option for a single error message, see if that  
 * Check compilation with dietlibc(http://www.fefe.de/dietlibc/) and uclibc(http://www.uclibc.org/):  
         · How to compile with these libraries  
         · Does this actually improve the binary size?  
         · Check warnings  
 * valgrind and friends  
101  * Write automated tests to test all these nifty corner cases. Either a test webserver or LD_PRELOAD injection of all syscalls (see libfake*)  * Write automated tests to test all these nifty corner cases. Either a test webserver or LD_PRELOAD injection of all syscalls (see libfake*)
102  * Write a helper script that displays the final binary size for different configurations to determine what a particular feature costs  * Write a helper script that displays the final binary size for different configurations to determine what a particular feature costs
103    * Document and implement coding conventions, versioning scheme
Legend:
Removed from v.54  
changed lines
  Added in v.55
  ViewVC Help
Powered by ViewVC 1.1.5