Chris Ridd wrote:
The only thing I can imagine might be a potential problem is that the
IntermediateResponse sequence uses responseName/responseValue, so if
there's code trying to deal with both in the same way, that will fail.
Is there such code?
You are right. The problem is that the response to an extendedRequest
may be a intermediateResponse. That doesn't break any code, but forces
me to access the responseValue attribute directly (without using the
accessor).
I would change ASN.pm , add a response_value accessor to Extension.pm
and make response an alias for response_value.
Daniel
