Why Deno's HTTP server uses web standards - Quick Recap

Recall & Review

beginner

What does it mean that Deno's HTTP server uses web standards?

It means Deno's HTTP server follows the same rules and interfaces used by browsers and the web, making it easier to write consistent and compatible code.

beginner

Why is using web standards beneficial for Deno's HTTP server?

Using web standards helps developers reuse knowledge from browser APIs, improves interoperability, and reduces surprises when switching between client and server code.

intermediate

Which web standard interface does Deno's HTTP server use to handle requests and responses?

Deno's HTTP server uses the Fetch API interface, specifically the Request and Response objects, which are standard in browsers.

intermediate

How does following web standards affect code sharing between client and server in Deno?

It allows developers to share code easily because the same Request and Response objects work similarly on both client and server sides.

beginner

What is one real-life analogy for why Deno uses web standards in its HTTP server?

Like using the same electrical plug type in different countries makes it easy to connect devices, using web standards means code works smoothly across different environments.

What web API does Deno's HTTP server use to represent incoming requests?

A Fetch API's Request object

B Node.js HTTP IncomingMessage

C XMLHttpRequest

D WebSocket

Deno uses the Fetch API's Request object to represent HTTP requests, aligning with web standards.

Why does Deno prefer web standards for its HTTP server?

A To avoid using JavaScript

B To make code compatible with browsers

C To use older, deprecated APIs

D To require special plugins

Using web standards makes server code more compatible and familiar to developers who work with browsers.

Which of these is NOT a benefit of using web standards in Deno's HTTP server?

A Requires learning a completely new API

B Better interoperability

C Easier code sharing between client and server

D Consistent behavior across environments

Using web standards means developers do NOT need to learn a completely new API; they reuse familiar ones.

Deno's HTTP server response is created using which web standard object?

A Socket

B XMLHttpRequest

C Response

D EventSource

Deno uses the Response object from the Fetch API to create HTTP responses.

What real-life example helps explain why Deno uses web standards?

A Writing code only for one browser

B Using different languages for each device

C Building a new type of electrical socket

D Using the same plug type in different countries

Using the same plug type everywhere is like using web standards to ensure compatibility.

Explain why Deno's HTTP server uses web standards and how it benefits developers.

Think about how using the same rules helps different parts work well together.

Describe the role of the Request and Response objects in Deno's HTTP server and why they follow web standards.

Consider how these objects are used both in browsers and Deno.

Practice

1. Why does Deno's HTTP server use web standards like the Fetch API?

easy

A. To make server code familiar and easier to share with client code

B. To force developers to learn a new, unique API only for Deno

C. To improve server speed by using non-standard protocols

D. To prevent compatibility with browsers and other runtimes

Solution

1. Step 1: Understand the use of web standards in Deno

   Deno uses web standards like the Fetch API so developers can write code that feels familiar from the browser environment.

2. Step 2: Recognize the benefit of sharing code

   Using the same APIs on server and client makes sharing code easier and reduces bugs caused by different APIs.

3. Final Answer:

   To make server code familiar and easier to share with client code -> Option A

4. Quick Check:

   Web standards = Familiarity + Sharing [OK]

Hint: Web standards mean same code works client and server [OK]

Common Mistakes:

• Thinking Deno uses unique APIs only
• Believing web standards slow down the server
• Assuming web standards prevent browser compatibility

2. Which of the following is the correct way to create a basic HTTP server in Deno using web standards?

easy

A. import { createServer } from "deno_http";
createServer((req, res) => res.end("Hello"));

B. import http from "deno_http";
http.createServer((req, res) => res.send("Hello"));

C. import { serve } from "https://deno.land/std/http/server.ts";
serve(() => new Response("Hello"));

D. import { listenAndServe } from "deno_std";
listenAndServe((req) => "Hello");

Solution

1. Step 1: Identify the official Deno HTTP server import

   Deno's standard library provides the 'serve' function from "https://deno.land/std/http/server.ts" which uses web standards.

2. Step 2: Check the server creation syntax

   The correct syntax is calling serve with a handler function returning a Response object, matching web standards.

3. Final Answer:

   import { serve } from "https://deno.land/std/http/server.ts"; serve(() => new Response("Hello")); -> Option C

4. Quick Check:

   Use 'serve' + Response for Deno HTTP server [OK]

Hint: Use 'serve' from Deno std with Response object [OK]

Common Mistakes:

• Using Node.js style imports or APIs
• Calling res.end or res.send which are not web standard
• Importing from incorrect or non-existent modules

3. What will the following Deno HTTP server code output when accessed?

import { serve } from "https://deno.land/std/http/server.ts";
serve(req => {
  if (req.method === "POST") {
    return new Response("Posted!");
  }
  return new Response("Hello World");
});

medium

A. Always responds with "Posted!"

B. Responds with "Hello World" for GET and "Posted!" for POST

C. Throws an error because method check is invalid

D. Responds with "Hello World" for POST and "Posted!" for GET

Solution

1. Step 1: Analyze the request method check

   The code checks if the request method is "POST" and returns "Posted!" in that case.

2. Step 2: Understand the default response

   If the method is not "POST", it returns "Hello World". So GET requests get "Hello World".

3. Final Answer:

   Responds with "Hello World" for GET and "Posted!" for POST -> Option B

4. Quick Check:

   POST = "Posted!", others = "Hello World" [OK]

Hint: Check req.method to decide response text [OK]

Common Mistakes:

• Assuming all requests respond with "Posted!"
• Thinking method property is invalid or missing
• Mixing up POST and GET responses

4. Identify the error in this Deno HTTP server code snippet:

import { serve } from "https://deno.land/std/http/server.ts";
serve(req => {
  req.respond({ body: "Hello" });
});

medium

A. Using req.respond is incorrect; should return a Response object

B. Missing await keyword before req.respond

C. serve function is not imported correctly

D. Response body must be a Uint8Array, not a string

Solution

1. Step 1: Check the method used to send response

   The code calls req.respond, which is from older Deno APIs and not compatible with the web standard serve function.

2. Step 2: Understand the correct response pattern

   In the current Deno HTTP server, the handler must return a Response object instead of calling req.respond.

3. Final Answer:

   Using req.respond is incorrect; should return a Response object -> Option A

4. Quick Check:

   Return Response, don't call req.respond [OK]

Hint: Return Response object, don't call req.respond [OK]

Common Mistakes:

• Using old Deno APIs with new serve function
• Forgetting to return a Response
• Confusing async handling with req.respond

5. How does using web standards in Deno's HTTP server help reduce bugs when sharing code between client and server?

hard

A. Because web standards prevent any runtime errors

B. Because Deno automatically converts server code to client code

C. Because web standards force all code to be synchronous

D. Because both environments use the same APIs, reducing differences and surprises

Solution

1. Step 1: Understand the role of shared APIs

   Using the same web standard APIs on client and server means developers write similar code for both sides.

2. Step 2: Recognize how this reduces bugs

   When APIs match, fewer surprises happen due to different behaviors or missing features, reducing bugs.

3. Final Answer:

   Because both environments use the same APIs, reducing differences and surprises -> Option D

4. Quick Check:

   Same APIs = fewer bugs [OK]

Hint: Same APIs client/server means fewer bugs [OK]

Common Mistakes:

• Thinking Deno converts code automatically
• Believing web standards force sync code
• Assuming web standards eliminate all runtime errors