Fetch called after pass

[Poul-Henning Kamp]

Hi Andre,

The state diagram has morphed a bit lately, DES is busy updating the
documentation and hopefully this will be covered RSN.

In the meantime, here is a snapshot of the current -trunks stateenginge:

	http://phk.freebsd.dk/misc/_.pdf

This is machine generated, see comment at the top of cache_center.c

We collapsed the pass and fetch code, after all, it does the same
basic thing, the distinction is only what happens to the object
afterwards: is it cached or thrown away.

That way we eliminated a lot of almost, but not entirely identical
code and got rid a number of problems in the pass version of the
code, that were already fixed in the fetch version.

So short version: yes, pass goes on to fetch (and now from there
to deliver), but the object is not cached.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.