feat: add http-client design doc

[viraatc]

What does this PR do?

Type of change

• Bug fix
• New feature
• Documentation update
• Refactor/cleanup

Related issues

Testing

• Tests added/updated
• All tests pass locally
• Manual testing completed

Checklist

• Code follows project style
• Pre-commit hooks pass
• Documentation updated (if needed)

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new design document for an HTTP client, providing comprehensive architectural and implementation details. This addition aims to centralize critical design information, ensuring clarity and consistency for future development and maintenance efforts. The document is stored using Git LFS to manage its size effectively within the repository.

Highlights

• New Design Document: An HTTP client design document has been added to the docs/html directory, outlining the architecture and implementation details for the client.
• Git LFS Configuration: The .gitattributes file was updated to include the new HTML design document under Git Large File Storage (LFS) tracking, ensuring efficient handling of large binary files.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .gitattributes
  • Added a Git LFS rule for HTML files in the docs/html directory.
• docs/html/http_client_design.html
  • Added the HTTP client design document as a Git LFS tracked file.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request since its creation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a design document for an HTTP client as a large HTML file tracked by Git LFS. While using Git LFS for large files is appropriate, committing generated documentation files to the repository is not ideal for maintainability and reviewability. I've suggested an alternative approach of committing the documentation source file instead and generating the HTML in a separate process.

[Copilot]

Pull request overview

Adds an HTTP client design document to the repository and configures Git LFS tracking for HTML files under docs/html/.

Changes:

• Add docs/html/http_client_design.html (stored as a Git LFS object).
• Update .gitattributes to track docs/html/*.html via Git LFS.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/html/http_client_design.html	Adds the design doc as an LFS-tracked HTML artifact (PR shows an LFS pointer).
.gitattributes	Routes docs/html/*.html through Git LFS filters.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.