Update to 0.85.3, and switch to using glib2.

- Version 0.85.3

- fix the unfairness of upload/download speed limit. In previous version, most
  of the time, a transfer obtains nearly all the bandwidth available.

- client can establish connection through web proxy.

- new flag added: -C. This flag is used to provide the address and port of the
  web proxy to use.

- fix a bug crashing the client if it uses glib2.x (glib1.2 version is not
  affected).

- fix GDL type detection problem preventing attachment of broken GDL.

- .sub added to file type "doc" (most of the time, these files contains
  subtitles).

- remove numerous old debug messages.

- 2 new commands added: /GDLMETDIR and /GDLMETPOLL. Using them, DCTC can use
  some informations obtained by the e-donkey emule client (partial CRC in .met
  files).

  -----------

- Version 0.85.2

- .iso, .bin, .cue and .img added to the file type "exe".

- fix a bug occuring when a broken GDL with L0CRC is available.

- fix a bug occuring when attaching a broken GDL with L0CRC (L0CRC was lost).

- new flag added: -m . If this option is set, DCTC will automatically append a
  dc++ like tag to your description.

- fix a configuration problem when detecting MD* functions.

- fix a hanging problem occuring when an UI disconnects when DCTC sends lot of
  messages to it.

- UADDR handles smarter incoming IP without known name. It prevents duplicated
  IP with IP with known name. To increase efficiency, it also tries a set of
  well known ports accepting DC connection.

  -----------

- Version 0.85.1

- the old md5 support was removed (option: -5).

- hublist handles an environment variable named "HUBLIST". In this variable, you
  can put all the hublist URL you want to use, use [tab] as separator. If the
  variable is not defined, the default direct connect hublist is used.

- hublist supports bzip2 list.

- fix typo in dctc man pages. Add man page for hublist.

- timeout added to hublist to prevent long wait when a hublist server does not
  respond.

- new program added: dctc_gdl123. This program takes 2 corrupted GDLs of the
  same files and rebuild a partial GDL containing only identical parts of the 2
  corrupted GDLs.

  -----------

- Version 0.85.0

- periodically send something to the hub is no network activity exists. This is
  required else the hub will close the connection.

- new command added: /GDLCRC, /GDLNOCRC. Using them, you can set a CRC on a GDL.
  DCTC computes CRC in the same manner has e-donkey 2000 does thus you can use
  its CRC (a 32 characters string composed of 0,1,...9,A,...,F values). The CRC
  allows detection of corrupted file but it does not provide corrupted data
  recovery. (see Documentation/DCextension/ed2k_crc file).

- minor change in the GLSTC format. To keep compatibility with gtk 1.2 version,
  no field is added. If a GDL CRC exists, it is appended to the script to start
  field, you will see a " &CRC:" field inside it.

- new flag added: -Z. When used, the given parameter is a directory that will
  be used instead of the default $(HOME)/.dctc directory.
  Patch by Henrique do N. Angelo (phpDC project).

- fix g_string_sprintf[a] compilation problem with glib2.

- flag -m is removed. DCTC now always works in extended mode.

- Add support of DC protocol extension commands: MD4Get0 and MD4Set. When
  connected to a compatible hub, you can send or retrieve partial CRC allowing
  detection of corruption of part of files. (see Documentation/DCextension/
  ed2k_crc file).

WARNING: the CRC computation has 2 effects:
--------
      1) If someone asks your client a CRC of a file you have not yet computed,
         DCTC will freeze during the computation (problem will be solved in
         future release). The computation of the CRC of 450MB file tooks
         approximately 15 seconds on my XP1700+.
         Note: only the main thread will be busy, download/upload won't be
         stopped.
      2) the speed of CRC computation and of the splitting of the faulty file
         is done at full speed thus you will have a lot of disk I/O. If you
         burn a CD on a non burn-proof CD writer, the burning process will
         probably be interrupted. On my test computer (athlon XP1700+, 768MB
         RAM, UDMA100 7200rpm disk), when reparing a 450MB file, I have
         encountered a freeze of 0.5 second due to the high I/O load.

- '*.mid' files are known recognized as audio file.

0 files changed, 0 insertions, 0 deletions