actually, the observed behavior (not propagating the exceptions) is *after* having sent OPTION_REQ with "exceptions". Also, the protocol document doesn't state any deprecation note...
The WORK_WARNING/WORK_FAIL combination feels a bit awkward -- could you explain a bit the reasoning behind deprecating WORK_EXCEPTION?
Hi Eric,
actually, the observed behavior (not propagating the exceptions) is *after* having sent OPTION_REQ with "exceptions". Also, the protocol document doesn't state any deprecation note...
The WORK_WARNING/ WORK_FAIL combination feels a bit awkward -- could you explain a bit the reasoning behind deprecating WORK_EXCEPTION?