Skip to main content
news

Re: Paintshop and Corel

Tony Cooper
SubjectRe: Paintshop and Corel
FromTony Cooper
Date11/25/2013 16:23 (11/25/2013 10:23)
Message-ID<m3o699lcu5nkmjftqpss3pdj3bvv0mfkfg@4ax.com>
Client
Newsgroupsrec.photo.digital
FollowsSandman
FollowupsSandman (17m) > Tony Cooper

On 25 Nov 2013 07:04:08 GMT, Sandman <mr@sandman.net>wrote:

Sandman
In article <2013112421034119589-savageduck1@REMOVESPAMmecom>, Savageduck wrote:

nospam
not really, and that link is titled 'what is your backup plan', not 'what is your backup protocol'.

i've been in the tech industry for a few decades, i have not heard the term 'backup protocol'. it's normally called 'backup strategy' or 'backup plan', which your link confirms in its title.

Savageduck
I use the term "protocol" in many different situations including referring to my back-up plan, method, etc. as my "Back-up protocol" especially when it comes to back-up on a road trip. Then I have referred to it as my "Triple Redundant Back-up Protocol" when using my Colorspace UDMA, MBP, & FW800 1TB portable HDD. I have written that in these photo NGs many times

Sandman
That's my interpretation of the term as well, that a "backup protocol" is something you execute manually. LIke you when on the road, you have a backup protocol (written down or in your head) of the steps you have to take to ensure that your data is backed up correctly.

A "protocol" is the standard way something is done. While you may determine the steps in your head, it isn't a protocol until it's initiated and put into place. The fact that you initiate certain steps manually doesn't change anything. If you manually change the back-up to go to device B instead of device A, you are still following the protocol because the protocol says you must manually designate a change in destination devices.

But when you get home and offload the images to your Mac, the automatic backup to Time Machine is presumably not one of your "backup protocols" since it¨'s all done automatically and without you having to do anything.

Jeez. I don't know if you just wanted to put your oar in and did so without thinking, or you are really this stupid.

How do you think an "automatic" process comes to be? Someone first decides what the process will be, and then writes it into the system. The back-up protocol was determined by the developers of the Time Machine program and installed it to do the back-up automatically in the future. The "automatic" function is part of the protocol.

When the steps are determined by the developer, and written into the program, a protocol has been established so the action will always be the same. That's a protocol. A protocol may include user-defined option choices like where the back-up is to go, and the location may be changed, but the protocol provides a tree to include these choices.

There can be two levels of back-up protocol. One level is what the developer includes in the system and the second level is the protocol the user follows. The user-determined protocol can be the "where" and "when" options of the future automatic actions. The developer-determined protocol includes providing the users with a way of choosing these options.

I have to laugh at your ignorance of what "automatic" means. You seem to think that the machine decides what will be done. The developer decides what is to be done, includes that in the program, and includes a step that makes that action always done in the future or allows a user decision to do a different action in the future. All "automatic" actions are manually determined at some point and only automatic after that.

I expect you to argue these points. In fact, I'm looking forward to seeing just how silly you can be in coming up with an argument. nospam has already contributed some silliness, but you can add to the entertainment.

-- Tony Cooper - Orlando FL