On Tue, Jul 24, 2018, 6:04 AM <yitzc...@coapp.co.il> wrote: > When an iotivity client tries to connect to the cloud, it tries to open a > socket using nonblocking io, as can be seen here: > > https://github.com/iotivity/iotivity/blob/50e57ef6c448ab8839b8a057a2817b82c37fcfdb/resource/csdk/connectivity/src/tcp_adapter/catcpserver.c#L918 > > This means that when trying to connect to the cloud, if there is no > connectivity, we it can take a very long time, if at all, to get the > failure callback. > > Is this behavior by design?
Yes. Or no. I guess you're asking if there is a good reason for that design. Dunno, but if you have an idea to improve it, please do. > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9799): https://lists.iotivity.org/g/iotivity-dev/message/9799 Mute This Topic: https://lists.iotivity.org/mt/23801764/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
