Subject | Re: Paintshop and Corel |
From | Tony Cooper |
Date | 11/27/2013 05:11 (11/26/2013 23:11) |
Message-ID | <dkra99d4abl4o59bgdv6f5r57vcjo72cam@4ax.com> |
Client | |
Newsgroups | rec.photo.digital |
Follows | J. Clarke |
J. ClarkeYou're the first to offer an explanation, rather than just a denial or argument, so I'll accept your version.
In article <ln1a99l8do45a63svi40iuv6be85u8thb2@4ax.com>, tonycooper214 @gmail.com says...Tony CooperJ. Clarke
On Tue, 26 Nov 2013 14:54:57 -0500, "J. Clarke" <jclarkeusenet@cox.net>wrote:J. ClarkeTony Cooper
Tony, just a comment here but someone working in IT would typically use "policy" to describe what you are referring to as a "protocol", which could be part the reason that people are being so argumentative.
I don't know that usage. I'm not involved in IT in any way, so if there's a jargon use for "policy", then it's new to me.
I'd appreciate a definition of "policy" as it applies to IT work. Preferably, a definition in your own words rather than a link. Link definitions tend to contain references that need definitions.
To me, a "policy" would be a set of regulations that determine how a situation will be handled. A "protocol", though, is a set of steps that will be followed in performing a task. A policy determines what people do, but the protocol determines what a program does.
Correct me if I'm wrong about a policy in an IT context.
A "policy" would be a set of rules established by an administrator. It might be in the form of written instructions to users or it might be something that is enforced by the system but is often a combination of both. So a backup policy might include setting the backup program to kick off every night at 2 AM and do a differential backup of all machines on the system, with a memo that some designated person is to change out the tapes or backup disks or whatever every afternoon before he goes home.