3 URGENT ---------------------------------------------------------------
6 IMPORTANT ------------------------------------------------------------
10 Part of the regression suite should be making sure that we don't
11 break backwards compatibility: old clients vs new servers and so
12 on. Ideally we would test the cross product of versions.
14 It might be sufficient to test downloads from well-known public
15 rsync servers running different versions of rsync. This will give
16 some testing and also be the most common case for having different
17 versions and not being able to upgrade.
21 If the platform doesn't support it, then don't even try.
23 If running as non-root, then don't fail, just give a warning.
24 (There was a thread about this a while ago?)
26 http://lists.samba.org/pipermail/rsync/2001-August/thread.html
27 http://lists.samba.org/pipermail/rsync/2001-September/thread.html
31 Avoids traversal. Better option than a pile of --include statements
32 for people who want to generate the file list using a find(1)
37 Traverse just one directory at a time. Tridge says it's possible.
39 Can possibly also be smarter about memory use while looking for hard
40 links by reducing the refcount as we find alternative names.
44 Implement suggestions from http://www.kame.net/newsletter/19980604/
45 and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt
47 If a host has multiple addresses, then listen try to connect to all
48 in order until we get through. (getaddrinfo may return multiple
49 addresses.) This is kind of implemented already.
51 Possibly also when starting as a server we may need to listen on
52 multiple passive addresses. This might be a bit harder, because we
53 may need to select on all of them. Hm.
55 Define a syntax for IPv6 literal addresses. Since they include
56 colons, they tend to break most naming systems, including ours.
57 Based on the HTTP IPv6 syntax, I think we should use
62 which should just take a small change to the parser code.
66 If we hang or get SIGINT, then explain where we were up to. Perhaps
67 have a static buffer that contains the current function name, or
68 some kind of description of what we were trying to do. This is a
69 little easier on people than needing to run strace/truss.
71 "The dungeon collapses! You are killed." Rather than "unexpected
72 eof" give a message that is more detailed if possible and also more
77 Device major/minor numbers should be at least 32 bits each. See
78 http://lists.samba.org/pipermail/rsync/2001-November/005357.html
80 Transfer ACLs. Need to think of a standard representation.
81 Probably better not to even try to convert between NT and POSIX.
82 Possibly can share some code with Samba.
86 With the current common --include '*/' --exclude '*' pattern, people
87 can end up with many empty directories. We might avoid this by
88 lazily creating such directories.
92 Perhaps don't use our own zlib. Will we actually be incompatible,
93 or just be slightly less efficient?
97 Perhaps flush stdout after each filename, so that people trying to
98 monitor progress in a log file can do so more easily. See
99 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=48108
101 PLATFORMS ------------------------------------------------------------
105 Don't detach, because this messes up --srvany.
107 http://sources.redhat.com/ml/cygwin/2001-08/msg00234.html
109 According to "Effective TCP/IP Programming" (??) close() on a socket
110 has incorrect behaviour on Windows -- it sends a RST packet to the
111 other side, which gives a "connection reset by peer" error. On that
112 platform we should probably do shutdown() instead. However, on Unix
113 we are correct to call close(), because shutdown() discards
116 BUILD FARM -----------------------------------------------------------
120 AMDAHL UTS (Dave Dykstra)
122 Cygwin (on different versions of Win32?)
124 HP-UX variants (via HP?)
128 NICE -----------------------------------------------------------------
132 Re-read config file (just exec() ourselves) rather than exiting.
134 --no-detach and --no-fork options
136 Very useful for debugging. Also good when running under a
137 daemon-monitoring process that tries to restart the service when the
140 hang/timeout friendliness
146 Change to using gettext(). Probably need to ship this for platforms
149 Solicit translations.
155 Write a small emulation of interactive ftp as a Pythonn program
156 that calls rsync. Commands such as "cd", "ls", "ls *.c" etc map
157 fairly directly into rsync commands: it just needs to remember the
158 current host, directory and so on. We can probably even do
159 completion of remote filenames.