The current module supports some CCK FileFields, but the field names are hard-wired in to the module. To keep things simple, for now it would be good to allow users to specify *one* CCK FileField (can have unlimited entries, so we'll need to loop through them) to be served *either* as an FTP link or as base64_encode()'ed data.

The module already supports FTP server settings, and that works (that's how my current client is doing it, because some files are videos of 100MB+, so base64_encoding them causes PHP to run out of memory... fast!) - most of the code for base64 is there, it just needs tidying - in fact, it was working perfectly. I'm just being cautious because I don't know it's current state.

This is still appropriate for cases where an article is only accompanied by one (or a few) small JPG images. So we should finish it off and get it working.