On 09/10/2015 11:07 AM, Schulhof, Gabriel wrote: > Hi! > > I'm wondering if this is a known/already-fixed issue: > > I'm finding that the resourceUri in a response to a presence request > is not set. In fact, the resourceUri field of the OCClientResponse > structure is neither initialized to null nor accessed in > HandlePresenceResponse() at all (AFAICT). > > Now, the resourceUri may not be very interesting for presence > requests, but in the process of writing the node.js bindings, I have > to traverse the structure fully in order to put together the > corresponding JavaScript structure. > > Additionally, numRcvdVendorSpecificHeaderOptions is not initialized > either, so I have to validate in the bindings to make sure it's not > greater than MAX_HEADER_OPTIONS. > > So, has this been fixed since then?
I'm not sure of all cases, but I believe there is a change going through review now that addresses at least some resourceUri setting in error responses. https://gerrit.iotivity.org/gerrit/#/c/2454/ -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com
