Program verify

["Reeve Fritchman" <reeve@xxxxxxxxxx>]

This is a nice function the cache function is a little clumsy.  It might be
more useful with a few small modifications.

"Refresh cache" should offer "yes", "no", and "smart".

"Yes" works the same as it appears to today: everything's reloaded.
"No" works the same as it appears to do today: nothing's reloaded.
"Smart" tells CODE/400 to compare the creation date of cached objects or the
last-changed date of cached source with the creation date/last-changed date
of host object/source, if the host is available.  Only host objects newer
than the cached versions would be downloaded.

This functionality should shorten the refresh time substantially when only
one external object is changed (a prototype, for example).  Now the whole
shootin' match has to be reloaded; this is fine if you're around the corner
from your iBox and running 100 MB/sec networks.  Some of us work through
Internet connections, and any kind of Internet connection is slow when
you're downloading lots of little files.

Another possibility: how about defining an interface to the piece of
CODE/400 that reaches out and touches the iBox so we could build our own
refresh mechanisms?

Regards,
Reeve