Andy,

Hi! The resource type should be opaque. This means that the stack does not
care. The upper layer might, but not the stack.

That said, the resource and interface types have namespaces and you should
not use ?core.*? unless you are implementing a CoRE WG resources. You
should also not use ?oc.*? since it is abandoned in the standards
specification. You should only use ?oic.*? if you are referring to
standard type.

The issue has not been through the bug scrub which is why I have not looked
at it yet.

Pat



From: [email protected] [mailto:iotivity-dev-
bounces at lists.iotivity.org] On Behalf Of ???
Sent: Monday, April 06, 2015 2:51 AM
To: "Lankswert,Patrick<patrick.lankswert"@intel.com
Cc: iotivity-dev at lists.iotivity.org; "Kesavan,
VijayS<vijay.s.kesavan"@intel.com
Subject: [dev] Fwd: server crashed by presence check



Hi Pat,
This is Andy.



One week before, my collegue Jack(JaeKeun) has been registered new issue
regarding presence check routine(active discovery?).
But there are no responses yet.


When we use some specific resource type and uri then stack crashed.
We think if we include the term 'core' within resource type and uri, this
problem can be occured. 

But we are not sure.
Since this situation is related with abnormal termination of software, I
think this is critical defect.
If we need to avoid to use the term 'core', the suitable guide should be
provided.
However if this kind of guide provided, still termination of software shall
be avoided.



Please review this issue.
https://jira.iotivity.org/i#browse/IOT-433



Regards
Andy





------- Original Message -------

Sender : ???<jjack.lee at samsung.com <mailto:jjack.lee at samsung.com> >
S4(??)/??/IoT Solution Lab(S/W??)/????

Date : 2015-04-01 16:47 (GMT+09:00)

Title : [dev] server crashed by presence check

To : iotivity-dev at lists.iotivity.org <mailto:iotivity-
dev at lists.iotivity.org>  







I found a error, and register issue to jira.



I test ocserver.cpp sample.
(location : csdk\stack\samples\linux\SimpleClientServer)


I only changed resourcetype and uri parameter in OCCreateResource() but It
was crashed.

I think "core" word lead to crash but not sure. 



please refer to below usage and jira link.



OCStackResult res = OCCreateResource(&(lightResource->handle),
"core.hubcore",
"oc.mi.def",
"/a/hubcore",
OCEntityHandlerCb,
OC_DISCOVERABLE|OC_OBSERVABLE);



https://jira.iotivity.org/browse/IOT-433



Thanks.



Regards,

Andy Minho Lee






--------



Lee Min Ho
Principal Engineer

IoT Solution Lab.
Web & Convergence Team
Software Center
SAMSUNG ELECTRONICS CO.,LTD

TEL . 82-31-279-7888
FAX . 82-31-279-0523
Mobile . 82-10-6228-8340
E-Mail . minho03.lee at samsung.com <mailto:minho03.lee at samsung.com> 












<http://ext.samsung.net/mailcheck/SeenTimeChecker?do=1dc10d3d9c28bbee01168e5
26931ac94b940e080c7ae4ed92829e26d6950518d4e60fcf6aeb61df594c3b6ddffd7613bcb2
38d00164b0be48eeb9bec5ad9c75d326bbdfb2ea96a2fcf878f9a26ce15a0> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150406/e29e01cc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13168 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150406/e29e01cc/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7198 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150406/e29e01cc/attachment.p7s>

Reply via email to