DioxusLabs/blitz

Add `ureq` backend to `blitz-net`

Open

#181 opened on Jan 20, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (152 forks)github user discovery
good first issue

Repository metrics

Stars
 (3,639 stars)
PR merge metrics
 (Avg merge 7h 25m) (50 merged PRs in 30d)

Description

The motivation for this is primarily as a binary size optimisation for apps that want networking but do not need 100s of connections and do not otherwise need tokio or an async executor in their stack.

The implementation should:

  • Be part of the existing blitz-net crate with feature flags for each backend
  • Use the new 3.x version of ureq
  • Split the reqwest and ureq implementations in separate files/modules
  • Use a threadpool to allow for multiple concurrent requests
  • Implement the blitz_net::get_text method as well as blitz_net::Provider

Contributor guide

Research direction
Study the existing reqwest backend structure in blitz net, then implement a similar ureq backend with feature flags, a threadpool for concurrency, and implement the required traits.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustfamiliarity with blitz net cratebasic knowledge of HTTP clients
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65