Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Constraints on the "success()" function of an http request?


PeterV959

Recommended Posts

When the success() function is executed after an http request, are there any constraints on what can be done within that function? I am not thinking about starting another http request, instead I wonder if I try to update my child devices as part of the function would be a problem. One thing that could happen (rarely, I hope, but still a possibility): if the child device had been deleted between iterations, my child device update procedure would create a new child device. So there is a minimal amount of overhead with simply updating the child device but probably twice as much overhead involved in the creation process. It strikes me that many of the examples of success() functions are short, sweet, and to the point. Currenty my development stores that data and deals with it on the next polling loop (about every ten seconds). But it also means that the device data is already ten seconds old when it gets updated. For my current devices the request/response time is short because it is on the same home network. I have another device I want to create that I am forced to go out to the cloud to control. That is not ideal but it is what it is.

 

Thank you for any assistance.

 

Peter

Link to comment
Share on other sites

17 hours ago, PeterV959 said:

When the success() function is executed after an http request, are there any constraints on what can be done within that function? I am not thinking about starting another http request, instead I wonder if I try to update my child devices as part of the function would be a problem. One thing that could happen (rarely, I hope, but still a possibility): if the child device had been deleted between iterations, my child device update procedure would create a new child device. So there is a minimal amount of overhead with simply updating the child device but probably twice as much overhead involved in the creation process. It strikes me that many of the examples of success() functions are short, sweet, and to the point. Currenty my development stores that data and deals with it on the next polling loop (about every ten seconds). But it also means that the device data is already ten seconds old when it gets updated. For my current devices the request/response time is short because it is on the same home network. I have another device I want to create that I am forced to go out to the cloud to control. That is not ideal but it is what it is.

 

Thank you for any assistance.

 

Peter

Not really, think about it as a function called from setTimout.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...