[Zope] Request regarding 'Hotfixes'

Bill Anderson bill@libc.org
26 Aug 2001 13:47:37 -0600


On Sun, 2001-08-26 at 10:33, Dieter Maurer wrote:
> marc lindahl writes:
>  > > A "hotfix" is called "hot" because ignoring it can be
>  > > a significant risk.
>  > > The name has nothing to do with the usual method to activate the
>  > > fix.
>  > 
>  > That's really stretching the meaning of the word hot...  
> But associating it with the runtime enhancement of Python
> classes (the "usual method to activate the fix") is stretching
> it *FAR* more....
> 

Not really. You are changing the behaviour of a Server without bringing it down. In the industry, this is commonly referred to as a hot thing.
Such as a HotSwap PCI Card Slot, or a HotSwapDrive, or in FibreChannel, HotSwapping a storage system.

In the Server world, Hot is usually referred to in terms of something being 'up'.

Similiar uses are hotSpare, or keeping HotFailover Server ready. of ocurse, we could also compare reboot
terms. Cold Start, Warm Reboot, Cold Reboot, temperature terms to indicate
readiness is actually quite common.

Hot is often, even in non-computer fields used to refer to something
being on. In the military, keeping a crew on standby often takes two forms, 
cold and hot. The hot are in the seat, ready to go, whereas
cold are offline, they are on a less-ready standby.

But anyway, this is part of the reasoning I gave for using Offline/Online.

Cheers,

Bill Anderson