Evelyn Hawke wrote:
A solution to this that was on another service I use for my web
organization was to make them into .filename files.... That
prevents anyone from being able to access them or read them without
actually being telnetted or FTP'd in, but they can still be used.
Would this work perhaps?
It would probably work, but like changing the file extensions to .cgi,
it would cause implementation problems due to non-compatibility with
previous versions.
I've been to a place or two where the cgi scripts were
web-viewable... they're only not web-viewable if the permissions
have been set correctly on the directory/file.
So, maybe hidden files are better.
Maybe I will consider anything like it for the next _generation_ of
Ringlink, i.e. not for the next _version_. After all, we have workable
solutions which are described in the FAQ.
Anyway, thanks Daniel and Evelyn for your suggestions.
/ Gunnar