Radha, There are a number of ways, but did you consider shortening your URIs? You are burning 242 bytes in URIs alone. We need to be able to support a lot of URIs, but performance will always be better if you keep your content constrained also. Pat
From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of P RADHABHAVANIGOWD Sent: Tuesday, August 18, 2015 3:56 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Multi Resource discovery payload issue Hi All, When we are creating more than 10 resources in same application. while sending resource discovery payload response for the discovery request received, We are getting "Payload too long" error on server side due to which client side we are not able to discover the created resource. Please find the attached logs for the same. List of Resource URIs URI of Resource 1: /oic/light/simulator/0 URI of Resource 2: /oic/light/simulator/1 URI of Resource 3: /oic/light/simulator/2 URI of Resource 4: /oic/light/simulator/3 URI of Resource 5: /oic/light/simulator/4 URI of Resource 6: /oic/light/simulator/5 URI of Resource 7: /oic/light/simulator/6 URI of Resource 8: /oic/light/simulator/7 URI of Resource 9: /oic/light/simulator/8 URI of Resource 10: /oic/light/simulator/9 URI of Resource 11: /oic/light/simulator/10 Next call to OCConvertPayloadHelper returned this code :0 Payload Size: 1103 Payload too long! We need support for resolving this error. Regards, Radha. [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=938ced2049aed55220ae5ad511534ca1d18ece5ffed09243c0c753a4395e22ae1e3bcc20668f5bc9525b67db19b927c7f5758e6fd014db2149e5ff3dfdc8681d76f80bf81d31c863cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150818/08697bb2/attachment.html>
