Does the no-delay option actually work?

Hello,

I have been experimenting with delay pools under version 2.1.PATCH1.

So far it seems to work according to expectations, except that having
the "no-delay" option set on a peer does not seem to make any
difference.

Specifically I have:

cache_peer bowerbird.cc.uq.edu.au sibling 80 3130 no-delay
...
delay_class1_access deny all
delay_class2_access allow wombat !LOCAL_OBJECTS
delay_class2_aggregate_restore -1
delay_class2_aggregate_max -1
delay_class2_individual_restore 300
delay_class2_individual_max 300

(And "client mgr:server_list" confirms that no-delay is set.)

As expected, requests which match the acl's go at 300 bytes/sec,
unless they are local hits, in which case they go at full speed.

But SIBLING_HITs from bowerbird.cc.uq.edu.au are also fed to the
client at 300 bytes/sec. Shouldn't they go at full speed, or am I
misunderstanding the meaning of the no-delay option?

--
Chris Teakle
Prentice Centre, University of Qld, Australia