diff options
| author | Anders Svensson <[email protected]> | 2017-04-30 19:21:38 +0200 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2017-06-13 13:50:06 +0200 |
| commit | 9d08b9d8d9d500259eeb808af19f9cf3d8d79fdf (patch) | |
| tree | e467155b147a967bc10d4ea703fef9f03857cd17 /lib/runtime_tools/examples/memory1.systemtap | |
| parent | 5f6d83776c38539e396bae345914be575aceea8d (diff) | |
| download | otp-9d08b9d8d9d500259eeb808af19f9cf3d8d79fdf.tar.gz otp-9d08b9d8d9d500259eeb808af19f9cf3d8d79fdf.tar.bz2 otp-9d08b9d8d9d500259eeb808af19f9cf3d8d79fdf.zip | |
Restore undocumented Failed-AVP setting convenience
The parent commit removed the convenience of setting something like the
following in the errors field of the diameter_packet of an answer
message.
[#diameter_avp{} = A2, {5001, #diameter_avp{} = A1}]
This results in Result-Code = 5001 and Failed-AVP = [A1,A2], but is
currently undocumented. Probably useful, so restore it.
Also accept {RC, [#diameter_avp{}]} at encode, which is probably more
useful; eg. [{5001, [A || {5001, A} <- Errors]}]
Anyone who wants full control can set errors = false and formulate
Result-Code/Failed-AVP themselves. (As opposed to not setting a value
explicitly, which results in setting from the decoded errors list. A bit
quirky, but documented and historical.)
Diffstat (limited to 'lib/runtime_tools/examples/memory1.systemtap')
0 files changed, 0 insertions, 0 deletions