> Check out the subject line: it's both grammatically twisted and > just plain unintelligible.
... > So the question is, how do we refer to such things in a way that is > specific and direct, but general enough to cover all apache users. > One possibility is to develop some specific terminology to cover this > user, define it, and use it consistently. The disadvantage to this > approach is that it adds an extra level of abstraction that must be > navigated by users. The subject line is one example, but I hate it. Any > other ideas? I prefer terms like 'http system user', 'system permissions' as suggested by nd. A terminoloy schould be easy to understand - Credentials imho isn't and I have no better one. Excatness as Michael wants can be reached by further description of the term. Kess --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
