This has the potential to sound fine and dandy for servers. I don?t think I can say the same for clients. Clients should be allowed to come and go as they please. And with that, they should be allowed to come and go gracefully.
Your phone should be allowed to interact with your smart office or your smart home using the same application and process in both places. With that, your phone may have enough context to suspend a session in either place (geo fencing, bluetooth connections, ?). Is this a case you can even build a certification test for? I suppose you could suspend a client and have the CTT tool look for the appropriate messages and come back into the session and continue the CTT battery of tests. That would have the same level of user interaction required during testing as tests for NOTIFY currently require. Thanks, Joey Morrow On 7/5/17, 8:59 AM, "Thiago Macieira" <thiago.macieira at intel.com> wrote: >On sexta-feira, 30 de junho de 2017 20:28:24 PDT Morrow, Joseph L wrote: >> Furthermore, I believe it may behoove us to implement a way to suspend the >> IoTivity stack. > >Please note that, as it stands, you cannot suspend an application for any >appreciable period of time and still pass OCF certification. > >The solution being discussed at OCF level for suspending applications, >shutting down radios and processors is to offload to an always on intermediary >device running on the same network. This will necessitate changes in OCF >certification, to distinguish always-on devices from sleepy ones. > >It's not an easy subject because it may need changes to the branding visible >to the end-user, as sleepy devices by themselves will not form a network. You >need at least one always-on. > >-- >Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > >_______________________________________________ >iotivity-dev mailing list >iotivity-dev at lists.iotivity.org >https://lists.iotivity.org/mailman/listinfo/iotivity-dev
