sight - nothing in the OCF spec
suggests
> that "protocol" in this case means "OCF protocol" vs. one or more foreign
> protocols. The word "protocol" is too imprecise here. If that's the
case, a
> little wording tweak could really help! I can propose
at understand the difference
> better than me.
>
> George Nash
>
> -----Original Message-
> From: iotivity-dev-boun...@lists.iotivity.org
> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Joo-Chul Kevin
> Lee
> Sent: Thursday, March 15, 2018 1:54 AM
form ID" instead of "piid" ?
Thanks
- Kevin
--
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Joo-Chul Kevin Lee, ETRI
161 Gajeong-dong, Yuseong-gu, daejon, 305-700, KOREA
E-mail: r...@etri.re.kr/cms.r...@gmail.com Tel: +82-42-860-1021
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ource Interface
> [CORE]). |
> ...|expected| Check 10. Every message with a payload body shall
> contain a Content-Format option with a numeric value from Table 32
> (12.2.3 Content Type negotiation [CORE]). |
> =========
>
> According
ndif
...
}
After removing preprocessor directives, server returns correct answers.
Is this a bug? or is there some reason?
Thanks & regards
- Kevin
--
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Joo-Chul Kevin Lee
Service Standard Research Team, PEC, ETRI
161 Gajeong-d
ivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
--
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Joo-Chul Kevin Lee, ETRI
161 Gajeong-dong, Yuseong-gu, daejon, 305-700, K
