My understanding is that the {"rep":{...}} part of each message is a
part of the specification for what makes an OCRepresentation, and is
thus necessary.

The "href":"" could potentially be ommitted, but I don't see why that
would be too big of a problem to ignore.

Finally, I note that you're showing JSON, the IoTivity stack uses CBOR
primarily now, so I was wondering if there is a translation happening
here, or if this is an older version of the code?

-Erich

On Fri, 2015-11-13 at 06:43 +0000, ??? wrote:
> Hi, 
> 
> We found a problem when we tested using a 'oic.r.mediaInput' resource.
> 
> The OIC Core Spec. addressed this resource should exchange array
> contains multiple source list.
> 
> We guess, IoTivity makes incompatible payload with specification.
> 
> You can see the details in Jira ( IOT-835,
> https://jira.iotivity.org/browse/IOT-835 )
> 
> And we think the patchset to resolve this problem should be applied
> before plugfest #5.
> 
> To release it very very quickly, developer who has ownership of this
> source code part would better create patchset.
> 
> Unfortunately, we don't know who is the right person..
> 
> Please help us...
> 
>  
> 
> [ IOT-835 ]
> 
> When exchanging data which data type is array between client and
> server,
> it always add "href" and "rep" in every array's element in OC stack
> layer.
> For example, when Client requests "GET" to Server, 
> (assume data payload which Server makes in application layer is like
> below.
> "ABC":[
> {"name":"name1","value":"value1"}
> ,
> {"name":"name2","value":"value2"}
> ,
> ] 
> -> ABC is vector<OCRepresentation>, and its elements are
> {"name":"name1","value":"value1"}
> and
> {"name":"name1","value":"value2"}
> )
> Client gets payload by server like this
> "ABC":[
> {"href" : "", "rep" :{"name":"name1","value":"value1"}},
> {"href" : "", "rep" :{"name":"name2","value":"value2"}}
> ]
> Problem is that "href" and "rep" is made automatically when making
> payload.
> Also, if client is not made of iotivity, and requests "POST" with
> array payload to iotivty Server, server can not parse payload that
> client sends. 
> 
> 
> 
>  
> 
> Thanks.
> 
> Best Regards,
> 
> ---
> 
> MyeongGi Jeong
> 
> Senior Engineer, Software Architect
> 
> Software R&D Center, Samsung Electronics Co., Ltd.
> 
> +82-10-3328-1130
> 
>  
> 
> 
> 
> 
> 
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to