Hi Folks,
Probably a question for Willy, but perhaps others worked on this code so
to the mailing list it goes.
I was curious as to why there is no sc_dec_gpc0 implemented in the sample
fetch / ACL code.
sc_inc_gpc0 does exist of course, and it's well-documented how it can be
used to mark an event(s) and use the value as a threshold for ACLs.
I had an idea of using that value as a counterbalance of two types of
traffic so as to use the gpc0 value as the differential between the two.
Request type A -> sc0_inc_gpc0
Request type B -> sc0_dec_gpc0
after which two requests, the gpc0 value would remain unchanged from the
original value.
However I quickly determined that there was no sc_dec_gpc0 feature.
Is there some architectural reason why this would be difficult or
impractical to do? Or is it just something that didn't seem
necessary/useful at the time?
Regards,
Mark Staudinger
Probably a question for Willy, but perhaps others worked on this code so
to the mailing list it goes.
I was curious as to why there is no sc_dec_gpc0 implemented in the sample
fetch / ACL code.
sc_inc_gpc0 does exist of course, and it's well-documented how it can be
used to mark an event(s) and use the value as a threshold for ACLs.
I had an idea of using that value as a counterbalance of two types of
traffic so as to use the gpc0 value as the differential between the two.
Request type A -> sc0_inc_gpc0
Request type B -> sc0_dec_gpc0
after which two requests, the gpc0 value would remain unchanged from the
original value.
However I quickly determined that there was no sc_dec_gpc0 feature.
Is there some architectural reason why this would be difficult or
impractical to do? Or is it just something that didn't seem
necessary/useful at the time?
Regards,
Mark Staudinger