- Document CS_DOTPALM, CS_PALMUSERNAME, CS_PALMSERIALNUM and CS_LOCALUSERNAME symbols. 
- Document CS-AutoLoad and CS-AutoSave conduit headers/arguments
- Add and document "init" type conduits.
- Document the SyncType conduit header.
- Document the noprompt config file option.
- Document the filter_dbs config file option.
- Investigate the exact meaning of modnum.
- Built-in conduits receive information about the PDA block (Keni's
  patch), but external conduits don't. It'd be nice if they did. The
  obvious way to do this is by sending them additional headers, e.g.:
	PDA-Name: Palm m105;
	PDA-Snum: 189X7M27GA63-N;		(done)
	PDA-Directory: /folks/arensb/.palm-m105;(done)
	PDA-Default: 1;				(done)
	PDA-Username: Gorko the Invincible;	(done)
	PDA-UID: 31337;
	PDA-DLPmaj: 1;
	PDA-DLPmin: 3;
- Add the PDA-xxx headers to the conduits development documentation.
- Add a warning about listen usb under linux.
- Fix --with-getlong 
- Review USB support in configure.in
- UDP wakeup packet support has been partially removed in one of the 
  latest patches because my Palm Desktop doesn't support/use it (?).
  It should eventually be re-implemented in an external program.
- Add documentation for long command line options.
- Add documentation for 'autoinit' option.
- Update the conduits development documentation to reflect changes
  in mandatory headers.
- Add documentation for 'cwd:' option in conduit{} block.
- Man page for coldnamed(8).
- Create a manifest file when installing, to help package-management
  utilities. Preferably add a rule to create the manifest without
  installing.
- Bug: when run from /etc/ttys, the Palm might suggest a speed that
  the serial port can't handle. But ColdSync doesn't notice this in
  time to send back a reasonable speed.
- Review Alessandro Zummo's SPC.pm. Add POD. Improve some of the
  identifiers.
- Perhaps add "force_fast" and/or "force_slow" .coldsyncrc options?
- Windows appears to use an ioctl() on the USB device to get the
  serial number. Is this possible here as well? If so, how to
  communicate this to the appropriate levels?
- Would it be possible to implement a web clipping server?
- Add a ~/.palm/commands file, containing commands to execute on the
  next sync. If absent, this should default to "sync". That way, you
  don't have to kill 'usbd' or 'getty' to do a one-time backup.
	Problem: what to do if the sync is aborted for whatever
  reason? Nuke the "commands" file? Delete only those commands that
  were successfully executed, and leave the rest for the next time?
  Perhaps have one file for permanent commands (e.g., if the user
  always wants to do a backup, or always wants to run some command
  after the sync) and one for one-shots?
	Allow execution of external programs.
- Should all of the Dlp*() functions return type dlp_stat_t instead of
  int?
- PConnection_net.c uses tini_slp() et al. even when it isn't
  appropriate. Better to add a pconn->tini() or pconn->unwind()
  method.
- Perhaps initialize $CS_CONDUIT_PATH to $PATH (from the environment).
- It'd be nice to add types to distinguish between bytes and letters,
  and between arrays of arbitrary data and strings of characters. This
  is for i18n and for the benefit of Japanese users and such.
- Use iconv(3) to convert command-line arguments to the appropriate
  encoding. Most Unix boxen use EUC for Japanese, but the Visor uses
  SJIS.
- Fix API bogosities in libpdb, libpconn.
- 'make install' should install libraries, headers.
- Redo error return status in {upload,download}_database() and
  friends, as per XXX comments.
- Separate i18n stuff for libpconn/libpdb into separate files. Figure
  out some way printing the appropriate messages ("coldsync" domain
  for the main program, "libpdb" for libpdb messages, etc.)
	dlopen() calls _init(). Can this be used?
- Separate libpconn and libpdb into separate packages.
	Separate i18n files.
- Consider allowing database-at-a-time syncing.
  Databases (or files?) named on the command line.
- Allow user to specify whether any "none" conduit
  should run before or after other conduits.
- Bug: run_mode_Daemon() apparently ignores serial number when looking
  in /usr/local/etc/palms. When syncing a visor, it recognizes

	|Andrew Arensburger|2072|arensb|Palm Pilot Pro
	10A813V96PC0-H|Andrew Arensburger|2072|arensb|Palm V
	*Visor*|Andrew Arensburger|2072|arensb|Visor

  though not

	109X7B28GC66-F|Gorko the Invincible|31337|arensb|Palm III|/folks/arensb/.coldsyncrc.test
- Rethink the Dlp*() functions.
	They return a DLPSTAT_* error code, but this makes
  error-checking rather hairy. Would it be better if they just set
  palm_errno and returned -1?
- Under Solaris, defining _XPG4_2 might induce standards-compliance,
  and make things happier. There's a comment in PConnection_net.c that
  says that this causes all sorts of other problems, though.
- With a Visor, if there's no pda{} block that matches exactly,
  ColdSync defaults to ~/.palm and username/userid from /etc/passwd.
	This seems like the Right Thing to do for the naive user, but
  means that if you've misspelled something in ~/.coldsyncrc , your
  stuff will go to the wrong place.
	Not sure what the fix should be. Add an "abort" pda flag,
  meaning "if you get this far, abort 'cos you overshot the real pda
  block"?
- When accepting a connection from a remote host, first open the TCP
  socket, and only then acknowledge the UDP packet. That way, if the
  TCP socket can't be opened for some reason, we can abort before
  acknowledging the UDP packet, and not promise the client a
  connection we can't offer. Besides, this is probably closer to what
  happens with inetd, where by the time the program is launched, inetd
  has already done most of the work of accepting the connection.
	Actually, it looks as if the UDP stuff is part of a completely
  different (name resolution? Windows?) protocol. If so, then ColdSync
  should only pay attention to the TCP stuff. The UDP name
  resolution(?) can be handled by a separate program, e.g. the one in
  pilot-link.
- Init mode should set the NetSync host and mask, if they're set in
  the pda block.
- "forward:" line in pda block: this is of the form
	forward: <destination> [<name>];
  where <name> is the name to use in NetSync wakeup packets. HotSync
  doesn't appear to use this anywhere else, which is why it's
  optional. Perhaps the server can multiplex based on the name it was
  given, like Apache.
	<destination> is usually a host name, though it can also be a
  host address, e.g., "192.168.1.2". Ideally, it should be possible to
  specify a network address and mask, e.g., "192.168.0.0/16"; or a
  network name, to be looked up with getnetbyname() (in this case,
  though, how do you get the mask?).
- "System MIDI Sounds.pdb" complains that
	I have a new, deleted record that is neither archived nor expunged
	What am I supposed to do?
  Investigate.
- NetSync forwarding: there's a comment in usb_select() hinting that
  select() on /dev/ugen0 is broken and always returns ready.
- NetSync should time out after a while: if no TCP connection received
  N seconds after accepting a UDP connection, stop waiting and abort.
	Should time out:
	- After sending response to UDP wakeup packet (waiting for TCP
  connection) (the wakeup may have been sent to a broadcast address,
  and the client decided to talk to another machine that responded
  first).
	- After sending UDP wakeup packet (no servers responding). Log
  this on the Palm.
	- Trying to establish TCP connection to server (it may be
  broken, only responding to UDP wakeup packets).
	- During the main part of the sync (server or client may be
  broken, stuck in infinite loop or something).
	- Probably other cases as well.
- Does NetSync support tickle packets? Or is this all handled by TCP?
- It'd be nice to have a tool to make sure that all files that CVS
  knows about are in the distribution somewhere.
- Add a SIGTERM handler, to catch Ctrl-C.
- Add support for TCP wrappers. RTFM hosts_access().
- Bug?: If the serial number matches (and is a real serial number),
  but the username/userid doesn't, ColdSync proceeds to the next
  entry. Arguably, this should be a definitive non-match.
- There ought to be cmp_init() etc., just as for the other protocols.
- Better description of ${prefix}/etc/coldsync.conf in the man page.
- Add support for CMP 2.0 (once I find a CMP 2.0 Palm)
- If hostid was set in /etc/coldsync.conf, it shouldn't be possible to
  override it in ~/.coldsyncrc.
- Persistent "Bad CRC" problems under Linux:
	As far as I can tell, the Linux serial driver is buggy, and
  drops characters. 'pilot-link' also sees bad CRCs; it just doesn't
  report them unless you compile with -DDEBUG.
	However, this isn't likely to be fixed any time soon, so need
  to increase robustness of ColdSync. In particular, make sure all
  sorts of insanity can be dealt with.
- Problem: old Palms, and Visors, don't have serial numbers. Hence, if
  a user has two Visors,
	coldsync -mI
  will find the first Visor PDA block listed in .coldsyncrc , and will
  (transparently and incorrectly) initialize from that, possibly
  clobbering existing information.
	Perhaps ought to be able to give the name of a PDA on the
  command line, e.g.:
	coldsync -mI "Second Visor"
- It might be nice to allow a conduit block to specify a name, rather
  than a creator/type pair, since those are usually more intuitive.
	Problem:
	conduit sync {
		type: fooX/barX;
		type: todo/DATA;
		name: FooBarDB;
	}
  How do "type:" and "name:" interact? Multiple "type:" lines are
  or-ed together. Should "name:" entries be or-ed as well?
	Counterintuitively, perhaps the "type:"s should be anded with
  the "name:"s. That is,
		type: aaaa/bbbb;
		type: cccc/dddd;
		name: FooDB;
		name: BarDB;
  means
		((type aaaa/bbbb) || (type cccc/dddd)) &&
		((name "FooDB")   || (name "BarDB"))

  This way, it's possible to express "databases of type xxxx/yyyy and
  with name "FooDB", which I don't think you can express under any
  other interpretation.
- Per-mode options
	It appears possible (under FreeBSD) to allow mode-specific
  options: have the getopt() loop in "config.c" stop after a
  "-m<mode>" option has been seen. Then, in run_mode_Foo():
	int arg;

	optind = opterr = 0;
	arg = getopt(argc, argv, <optstr>);

	It remains to be seen whether this is portable or not.
- Add a Bool check_palm_owner(pda_block, palm) (or something) function
  that verifies that the Palm (which is known to have the correct
  serial number) has the proper username/userid and whatnot. For
  standalone mode: if it doesn't match, don't sync.
- Bug: should be smarter about installing files: it'd be nice to make
  sure that there's enough memory.
- Possible feature: degraded-mode NetSync: if ColdSync is supposed to
  forward a connection to another host for NetSync, but can't, it
  could go into degraded mode: do a local sync to a temporary
  (mqueue-like?) directory, then try to sync with the real remote
  host.
	Is this even desirable? Would it cause problems if the user
  manages to sync with the real remote host before the local host
  manages to do so?
- Bug: Under FreeBSD, when both Visor and Rio 600 are plugged in,
  Coldsync doesn't find the Visor correctly.
- Add default flag to listen blocks.
- KDE korganizer just uses vCalendar format for both events and todo
  list. Uses special fields "X-PILOTID" and "X-PILOTSTAT", presumably
  for Palm syncing. Also "X-ORGANIZER:MAILTO:arensb@localhost", not
  sure what for.
	Find an appropriate Perl module to parse iCalendar format.
- Add a type for those four-letter creator types and such.
- Something to parse version numbers, as per <System/NetMgr.h> and
  <System/SystemMgr.h>
- Lock files while syncing.
- The daemon ought to have some way to communicate with actual users,
  so that they can be notified when a sync starts, be asked questions,
  and other fun stuff. OTOH, since this is Unix, it ought to be able
  to run unattended.
	Possibly the best way to do this is to have the daemon listen
  on a "control" port. Clients can connect to this port and be
  notified, or control the daemon.
	Maybe a Unix domain socket is the obvious way to do it, since
  then there's no question about which machine the connection comes
  from. If it's a TCP or UDP socket, however, you can monitor syncs
  going on on another machine (useful for nosy administrators?). Here
  again, TCP is probably more secure, but UDP is less likely to cause
  a problem if something dies.
- When a new database is installed, it might contain dirty records. At
  the very least, it needs to make its way to the backup directory. Of
  course, it's silly to upload the database, then download it again
  just for the sake of syncing it. Fix the conduit API (not just
  GenericConduit) to make sense in this situation.
	Presumably this is the equivalent of a slow sync, but don't
  bother downloading the database from the Palm.
- FreeBSD's /bin/sh is still broken (as of 4.0):
	echo "before"
	for dir in a b c; do
		test "$dir" = "." && echo "found dot"
	done
	echo "after"
  still exits right after the "done". Presumably, what needs to happen
  is for information about whether to exit with the "-e" flag to be
  carried upwards through the parse tree.
	Until this gets fixed, I don't want to use 'automake'.
- Should all of the library .h files be lumped under #include
  <palm/foo.h> ?
- In daemon mode, when setting the UID, use setuid() to set both the
  real and effective UID: once it is determined that this is
  "arensb"'s Palm, we want to relinquish all of our root-ly powers and
  become as much like "arensb" as possible.
	What about setgid()?
	What's initgroups()? Is it useful?
- "Timeout. Attempting to resend" when installing AmsterdamMaps.pdb
  (166368 bytes) (from Heineken's BarTrek package, or the PHP manual).
- There appears to be a timing(?) problem with 'xcopilot',
  specifically when terminating. ColdSync thinks everything is fine,
  but 'xcopilot' hangs. I think it thinks that ColdSync hasn't
  received the final ACK. If you give the data time to drain, it
  appears to work fine, though. Maybe it's just a problem with the tty
  devices.
- Additional arguments on command line: if an argument is of the form
  "FOO=bar", it should set the variable FOO to the value "bar".
- Should variables set in .coldsyncrc be propagated to the
  environment? Should this be done as soon as they're set, or when the
  conduit is run?
- Should send mail to the user with a report of the sync (in daemon
  mode). Probably just add an option for this.
- Conduit for MH alias file: look for lines of the form
	alias:	<address> Firstname Lastname
  (where the "<" and ">" are literal). If $record->{firstName} . " " .
  $record->{name} eq "Firstname Lastname", then update the e-mail
  address.
- If I ever find a database that uses sort blocks, for testing, it
  might be a good idea to sync them as well.
- Perhaps status codes 6xx can be used for machine-readable
  informational messages, e.g., "NN% complete".
- Write 'mung-script' (or something) utility that takes a script
  pathname and an interpreter path, and mungs the #! path work
  properly. Make sure to use "#!/bin/sh" and not "#! /bin/sh", as per
  portability comments in 'automake' documentation.
- No-brainer configuration: make "conduit -config" part of the spec.
  Allow the user to add "CS_CONDUITDIR=/conduit/dir" to .coldsyncrc.
  Then, when ColdSync runs, it runs "/conduit/dir/foo -config" for
  every conduit in /conduit/dir and saves the results in
  /conduit/dir/cache. /conduit/dir/cache is then read in, so that the
  configuration is the concatenation of ~/.coldsyncrc and
  /conduit/dir/cache.
	This way, if a new conduit is released, the naive user can
  just put it in /conduit/dir, and it'll work with its default
  configuration. A more sophisticated user can add a .coldsyncrc entry
  manually.
	Obviously, need the "final" flag in conduit blocks, to prevent
  unwanted conduits from running.
- The 'prompt_for_hotsync' argument to new_PConnection() is a hack.
  That whole function needs to be rethought. Would it be better to
  separate it into new_serial_PConnection(), new_usb_PConnection(),
  new_tcp_PConnection()? Or pass it a union that gives the
  connection-specific arguments?
- In config.c, when creating directories: ought to do ~-expansion on
  directory names: as in csh, only expand leading "~" or "~user".
- In .coldsyncrc, should be able to associate a name (or alias) with a
  pda block. In addition, should be able to specify that a given
  conduit block only applies to a given PDA.
- Installing new databases is suboptimal. Currently, it sends the
  database over, then later downloads it all over again. There's got
  to be a better way to do this.
	Try:
	Install the new database on the Palm.
	Write it (possibly under a new name) to ~/.palm/backup[1].
	Run fetch conduits.
	Run sync conduits.
	Run dump conduits.
  [1] What if the database already exists?

	Is it necessary or desirable to force a slow sync for this
  database?
- Improve fault-tolerance and error handling:
	Kill ColdSync with Ctrl-C. Have it send a valid cancel to the
  Palm.
	Fill the Palm up. See what happens.
- Dump conduit: read all of the completed "to do" items and append
  them to a text file, thus generating a status report. Optionally
  delete and/or expunge them.
- Fetch conduits: purge all completed "to do" items, and all
  appointments older than N days (where N is configurable).
	Delete and archive events by default. Allow an option to
  expunge them.
- If a conduit dies (e.g., "memo-kjots" with flavor "fetch"), should
  print an error message giving some indication of which conduit said
  that.
- Work on archive2pdb
	Figure out why it insists on writing the .pdb as "MemoDB" and
  not "MemoDB.pdb".
	Add lots of command-line options to set output file, select
  which records will be restored, etc.
	Ought to be able to delete records.
	A GUI front end would be nice.
- Fix ColdSync.pm so that "-config" will also print which preferences
  the conduit knows about.
- Consider an optimization: if the local database hasn't been
  modified, don't write it back to disk. This reduces the size of
  daily backups by a trivial amount, but will also make a couple of
  users happy.
	The obvious way to do this is to add a 'Bool dirty' flag to
  struct pdb. It is false initially. Fix the PDB manipulation
  functions such that they set the dirty flag if they modify the
  database.
	At the end of the local sync, if the dirty flag is still
  false, don't bother writing the database to disk.
- libpdb and libpconn are useful in their own right. Turn them into
  standalone packages. At least libpdb.
- Perhaps the job of communicating with the Palm can be done in a
  separate (Posix) thread? That way, that thread can deal more
  naturally and more single-mindedly with things (e.g., timeouts,
  unexpected data packets, etc.). In particular, it would be able to
  send tickle packets at appropriate intervals.
- ColdSync.pm should open SPC file handle as appropriate.
- Add some "pref" lines to sample.coldsync.rc
- Rewrite 'send-mail' as a Sync conduit.
- Do something with Daniel Klein's <bilderzeitung@hotmail.com> Doc
  stuff.
- The $VERSION stuff in the Perl modules doesn't handle branch
  versions: revision 1.2.3.4 will set $VERSION to "1.002", rather than
  "1.002_003_004", which might be desirable. Is it worth fixing this?
	Will Perl 5.6 make this comment obsolete?