Add Persistent Connection extension

[ryan-gang]

Introduce new stages for managing persistent HTTP connections, multiple concurrent connections, and explicit connection closure. Rename stages for improved clarity and consistency in naming conventions.

Summary by CodeRabbit

• New Features
  • Persistent Connections: The server now reuses open connections to handle multiple requests efficiently.
  • Concurrent Connections: Enhanced capabilities allow the server to manage several persistent connections simultaneously.
  • Explicit Connection Closure: Introduced controlled connection termination when the client requests closure.

[coderabbitai]

Walkthrough

The changes update the course-definition.yml file by adding three new stages that define specific behaviors for HTTP connection management. The new stages require the server to handle persistent connections by default, manage multiple concurrent persistent connections, and explicitly close connections when a Connection: close header is used. Each stage comes with its own set of tests to ensure the server adheres to HTTP/1.1 connection handling requirements.

Changes

File	Change Summary
course-definition.yml	Added three new stages: Persistent connection (slug: "ag9"), Multiple persistent connections (slug: "ul1"), and Connection closure (slug: "kh7").

Sequence Diagram(s)

Loading

sequenceDiagram
    participant Client1 as Client 1
    participant Client2 as Client 2
    participant Server as Server
    Client1->>Server: Initial Request (Keep-Alive)
    Server-->>Client1: Response (Keep-Alive)
    Client2->>Server: Initial Request (Keep-Alive)
    Server-->>Client2: Response (Keep-Alive)
    Client1->>Server: Follow-up Request
    Server-->>Client1: Response (Keep-Alive)

Loading

sequenceDiagram
    participant Client as Client
    participant Server as Server
    Client->>Server: Request (normal headers)
    Server-->>Client: Response (Keep-Alive)
    Client->>Server: Request with "Connection: close"
    Server-->>Client: Response (Connection: close)

Poem

I'm hopping along with joyful glee,
Updating connections, oh so free.
Persistent and grouped in a clever hop,
Multiple and closing, we never stop!
A little bunny cheers our PR’s glow 🐇✨.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8fb8027 and 72f4e23.

📒 Files selected for processing (1)

• course-definition.yml (1 hunks)

🔇 Additional comments (3)

course-definition.yml (3)

826-853: Persistent Connection Stage: Requirements and Test Flow Are Clear
The newly added stage with slug "ag9" clearly specifies the behavior expected for persistent HTTP connections, including the requirement to keep the TCP connection open between requests. The test instructions using sequential requests (with curl --http1.1) effectively describe the expected server behavior.

---

857-885: Multiple Persistent Connections Stage: Concurrent Handling Clearly Defined
The stage with slug "ul1" outlines the need for handling multiple concurrent persistent connections. The description and test instructions illustrate that each connection should be managed independently and remain open for multiple requests. This aligns well with the objectives for concurrent connection management.

---

889-921: Connection Closure Stage: Explicit Closure Rules Are Well Specified
The stage with slug "kh7" effectively details the expected behavior for explicit connection closure. It instructs that when a request carries the Connection: close header, the server should include the same header in its response and close the connection afterward. The test scenarios provided are comprehensive and ensure that both normal and closing behaviors are covered.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.