HTTP request methods for IoT (GET, POST, PUT) in IOT Protocols - Time & Space Complexity

Time Complexity: HTTP request methods for IoT (GET, POST, PUT)

O(n)

Understanding Time Complexity

When IoT devices communicate using HTTP methods like GET, POST, and PUT, the time it takes depends on how many requests are sent and processed.

We want to understand how the number of requests affects the total time spent handling them.

Scenario Under Consideration

Analyze the time complexity of the following IoT HTTP request handling code.

for request in requests:
    if request.method == 'GET':
        handle_get(request)
    elif request.method == 'POST':
        handle_post(request)
    elif request.method == 'PUT':
        handle_put(request)
    else:
        handle_other(request)
    log_request(request)

This code processes a list of HTTP requests from IoT devices, handling each based on its method.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each request in the list.
• How many times: Once for every request received.

How Execution Grows With Input

As the number of requests increases, the total processing time grows in direct proportion.

Input Size (n)	Approx. Operations
10	10 request handlings
100	100 request handlings
1000	1000 request handlings

Pattern observation: Doubling the requests roughly doubles the work done.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle requests grows linearly with the number of requests.

Common Mistake

[X] Wrong: "Handling different HTTP methods changes the overall time complexity."

[OK] Correct: Each request is still handled once, so the total time depends mainly on the number of requests, not the method type.

Interview Connect

Understanding how request handling scales helps you design efficient IoT systems and shows you can think about performance in real situations.

Self-Check

"What if we added nested loops to process each request's data items? How would the time complexity change?"

Practice

1. Which HTTP method is used to retrieve data from an IoT device without changing it?

easy

A. POST

B. DELETE

C. PUT

D. GET

Solution

1. Step 1: Understand the purpose of GET

   GET is designed to fetch or read data without modifying it on the server or device.

2. Step 2: Compare with other methods

   POST sends new data, PUT updates existing data, DELETE removes data. Only GET fetches without change.

3. Final Answer:

   GET -> Option D

4. Quick Check:

   GET = fetch data without change [OK]

Hint: GET fetches data, POST sends new, PUT updates existing [OK]

Common Mistakes:

• Confusing POST with GET as both send data
• Thinking PUT fetches data
• Using DELETE instead of GET for retrieval

2. Which of the following is the correct syntax to send data using POST method in an HTTP request for IoT?

easy

A. PUT /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22}

B. POST /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22}

C. GET /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22}

D. DELETE /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22}

Solution

1. Step 1: Identify the method for sending new data

   POST is used to send new data to the server or device, so the request line must start with POST.

2. Step 2: Check the syntax correctness

   The syntax includes the method, path, HTTP version, headers, and body. POST /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22} correctly uses POST with JSON data.

3. Final Answer:

   POST /device/data HTTP/1.1\nContent-Type: application/json\n\n{"temp": 22} -> Option B

4. Quick Check:

   POST sends data with correct syntax [OK]

Hint: POST method starts the request line to send data [OK]

Common Mistakes:

• Using GET method to send data
• Missing Content-Type header
• Using DELETE or PUT instead of POST for new data

3. Given this HTTP request to update a device setting:

PUT /device/settings HTTP/1.1\nContent-Type: application/json\n\n{"mode": "eco"}

What is the expected result on the device?

medium

A. The device mode is updated to 'eco'.

B. The device sends back current settings without change.

C. A new device setting is created without replacing existing ones.

D. The device deletes the current settings.

Solution

1. Step 1: Understand the PUT method purpose

   PUT replaces or updates existing data on the device with the provided data.

2. Step 2: Analyze the request body

   The JSON body sets "mode" to "eco", so the device's mode setting will be updated accordingly.

3. Final Answer:

   The device mode is updated to 'eco'. -> Option A

4. Quick Check:

   PUT updates existing data [OK]

Hint: PUT updates or replaces existing data on device [OK]

Common Mistakes:

• Thinking PUT only adds new data without replacing
• Confusing PUT with GET which fetches data
• Assuming DELETE is used to update data

4. You wrote this HTTP request to update sensor data:

POST /sensor/data HTTP/1.1\nContent-Type: application/json\n\n{"humidity": 45}

But the device does not update the data. What is the likely error?

medium

A. The JSON body is invalid.

B. Content-Type header is missing.

C. POST is incorrect; PUT should be used to update existing data.

D. GET method should be used instead of POST.

Solution

1. Step 1: Identify the purpose of the request

   The request aims to update existing sensor data, which requires the PUT method.

2. Step 2: Check the method used

   POST is for sending new data, not updating. Using POST here causes the device to ignore the update.

3. Final Answer:

   POST is incorrect; PUT should be used to update existing data. -> Option C

4. Quick Check:

   Use PUT to update data, not POST [OK]

Hint: Use PUT to update, POST to create new data [OK]

Common Mistakes:

• Using POST instead of PUT for updates
• Ignoring Content-Type header importance
• Confusing GET with POST for data changes

5. An IoT device API supports GET, POST, and PUT methods. You want to add a new temperature reading and then update the device's configuration mode. Which sequence of HTTP requests should you use?

hard

A. POST to add temperature, then PUT to update configuration

B. PUT to add temperature, then POST to update configuration

C. GET to add temperature, then PUT to update configuration

D. POST to add temperature, then POST to update configuration

Solution

1. Step 1: Identify method for adding new data

   POST is used to send new data, so adding a temperature reading requires POST.

2. Step 2: Identify method for updating existing data

   PUT updates or replaces existing data, so updating configuration mode requires PUT.

3. Step 3: Determine correct sequence

   First POST to add new reading, then PUT to update configuration.

4. Final Answer:

   POST to add temperature, then PUT to update configuration -> Option A

5. Quick Check:

   POST new data, PUT update existing [OK]

Hint: POST adds new, PUT updates existing; order matters [OK]

Common Mistakes:

• Using PUT to add new data
• Using POST to update existing data
• Using GET for data changes