Skip to main content
Software Engineering

Return to Question

Tweeted twitter.com/StackSoftEng/status/906643390124707841
grammar corrections
Source Link
edit approved Sep 9, 2017 at 14:47
Glorfindel
edit approved Sep 9, 2017 at 14:47
Glorfindel
  • 3.2k
  • 6
  • 26
  • 33

What is the right way to make http request according toHTTP requests when a sliderslider's value changes?

I am designing a basic software for smart wireless lighting systems, sofware. The software is GUI based, and I have a slider for the brightness setting of a light in my GUI, the. The lighting system has a RESTful API so I can listen theto changes on the slider value and make a httpan HTTP request with the value to the system. The thing is, it seems utterly naivenaïve to make new http requestHTTP requests with every single value change of value.

For example, if the user changes the slider value from 70 to 20, the software would make 50 httpHTTP requests.

How do people tackle this kind of problem do? Do I wait after each request for a defined duration? What is the best practice to overcome making almost a hundred requests?

What is the right way to make http request according to a slider value?

I am designing a basic software for smart wireless lighting systems, sofware is GUI based, and have a slider for the brightness setting of a light in my GUI, the lighting system has a RESTful API so I can listen the changes on the slider value and make a http request with the value to the system. The thing is, it seems utterly naive to make new http request with every single value change.

For example if the user changes the slider value from 70 to 20, the software would make 50 http requests.

How do people tackle this kind of problem do I wait after each request for a defined duration? What is the best practice to overcome making almost hundred requests?

What is the right way to make HTTP requests when a slider's value changes?

I am designing basic software for smart wireless lighting systems. The software is GUI based, and I have a slider for the brightness setting of a light in my GUI. The lighting system has a RESTful API so I can listen to changes on the slider value and make an HTTP request with the value to the system. The thing is, it seems utterly naïve to make new HTTP requests with every single change of value.

For example, if the user changes the slider value from 70 to 20, the software would make 50 HTTP requests.

How do people tackle this kind of problem? Do I wait after each request for a defined duration? What is the best practice to overcome making almost a hundred requests?

clarifying software is GUI based, slider is in the GUI
Source Link
Eralp Sahin
Eralp Sahin
  • 171
  • 5

I am designing a basic software for smart wireless lighting systems, sofware is GUI based, and I have a slider for the brightness setting of a light in my GUI, the lighting system has a RESTful API so I can listen the changes on the slider value and make a http request with the value to the system. The thing is, it seems utterly naive to make new http request with every single value change.

For example if the user changes the slider value from 70 to 20, the software would make 50 http requests.

How do people tackle this kind of problem do I wait after each request for a defined duration? What is the best practice to overcome making almost hundred requests?

I am designing a basic software for smart wireless lighting systems and I have a slider for the brightness setting of a light, the system has a RESTful API so I can listen the changes on the slider value and make a http request with the value to the system. The thing is, it seems utterly naive to make new http request with every single value change.

For example if the user changes the slider value from 70 to 20, the software would make 50 http requests.

How do people tackle this kind of problem do I wait after each request for a defined duration? What is the best practice to overcome making almost hundred requests?

I am designing a basic software for smart wireless lighting systems, sofware is GUI based, and have a slider for the brightness setting of a light in my GUI, the lighting system has a RESTful API so I can listen the changes on the slider value and make a http request with the value to the system. The thing is, it seems utterly naive to make new http request with every single value change.

For example if the user changes the slider value from 70 to 20, the software would make 50 http requests.

How do people tackle this kind of problem do I wait after each request for a defined duration? What is the best practice to overcome making almost hundred requests?

Source Link
Eralp Sahin
Eralp Sahin
  • 171
  • 5

What is the right way to make http request according to a slider value?

I am designing a basic software for smart wireless lighting systems and I have a slider for the brightness setting of a light, the system has a RESTful API so I can listen the changes on the slider value and make a http request with the value to the system. The thing is, it seems utterly naive to make new http request with every single value change.

For example if the user changes the slider value from 70 to 20, the software would make 50 http requests.

How do people tackle this kind of problem do I wait after each request for a defined duration? What is the best practice to overcome making almost hundred requests?