Bulgarian mirror 10 Gbps

PuTTY wish config-struct

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

Currently PuTTY uses a single struct (Config) containing a bunch of fixed-length buffers to store its configuration. This leads to problems such as limited space for port forwardings. It should clearly be replaced with a structure containing references to allocated storage.

This isn't entirely trivial, which is probably the main reason we haven't done it yet:

• Object housekeeping. Currently, when a Config needs to be duplicated intra-process, a structure copy is usually by and large adequate, with occasional grotty fixing-up of pointers. Similar issues apply to construction and destruction. We'd need to replace this with proper suite of object housekeeping functions.
• Serialisation. Currently `Duplicate Session' is implemented by squirting the struct over to another process and crossing our fingers. This is obviously icky, and clearly won't be sufficient when there are more pointers around.
  Any textual format we invent to store configuration in a file would probably be suitable for this too; so this should probably wait until we've done that (which we already have to some extent for the Unix port).
• Opaque objects. Some platforms may use opaque objects to represent things like filenames. These need to be copyable, serialisable etc.