Hi, Markus is completely right, that's exactly my problem. I was suspecting that discovery might be different, so I've tried to access the resources directly by their uri but I could make it work either (might simply be that I'm not using the right uri...).
here is what I've done: * launch simpleserver * launch simpleclient : it finds the server and displays the address (which means that the server is indeed working and serves requests just fine) In my case: coap://[fe80::5265:f3ff:feb8:58e1]:36137/a/light, the address is Link-local and the port seems to change on each server run * try to make a get on this address with a coap client, I've tried the command line client that ships with libcoap and copper : both fail at finding the resource. On the other hand, when I try copper with a libcoap server, it works very well. regards, Pierre On 10/30/2015 01:37 AM, Markus Jung wrote: > > Hello, > > I think Pierre means that a lot of CoAP related tools (e.g., Copper > plugin for Firefox) are not working with the basic IoTivity example > server applications. Regarding discovery OIC/IoTivity uses a different > approach than RFC 6690 (https://tools.ietf.org/html/rfc6690), so > discovery in Copper will not work. But execution of GET, PUT and POST > requests should be working. > > It would be great if the issue could be investigated by the discovery > & connectivity maintainers. It could indicate some incompatibility and > interoperability issues regarding the CoAP protocol. > > Best regards > > Markus > > ------- *Original Message* ------- > > *Sender* : Uze Choi<uzchoi at samsung.com> S6/Principal Engineer/IoT > Lab./Samsung Electronics > > *Date* : Oct 30, 2015 09:13 (GMT+09:00) > > *Title* : Re: [dev] Experimenting with iotivity resource sample > > Hi Pierre, > Could you share how you set the server, I mean specifically where you > get the fridge resource profile? > And which resource you want to access? > BR Uze Choi > > > ---?? ???--- > ??? : pierre.rust at orange.com > ???? : 2015/10/29 19:41 (GMT+09:00) > ?? : [dev] Experimenting with iotivity resource sample > > Hi, > > I'm currently investigating IoTivity, especially the way resources are > structured and represented. For that I've played a bit with the resource > examples ; these work well but imo they don't really reveal the > low-level structure of the resources used (with technical resources like > /oic/d, properties, etc.). These sample where probably not meant for that. > > Then I've tried to discover and inspect the resources exposed by these > example with CoAP clients (mostly copper, but I've tried other) and I > don't understand why none of these client seems to be able to discover, > nor access, these resources. And that even when I point them directly to > the uri printed out by the example ( e.g. > coap://[fe80::5265:f3ff:feb8:58e1]:34037/device for the fridge server). > > Am I missing something obvious here? Any help would be greatly > appreciated. > > thanks, > > Pierre > > -- > > Pierre Rust > Senior Software Developer > OLPS/SOFT/NEC > 06 76 88 75 28 > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les > messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a > ete altere, deforme ou falsifie. Merci > > This message and its attachments may contain confidential or > privileged information that may be protected by law; > they should not be distributed, used or copied without authorization. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, France Telecom - Orange shall not be liable > if this message was modified, changed or falsified. > Thank you. > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Pierre Rust Senior Software Developer OLPS/SOFT/NEC 06 76 88 75 28 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorization. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange shall not be liable if this message was modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151030/a454db55/attachment.html>
