bytecodealliance/StarlingMonkey

Optimize computing encoded `FormData` length

Open

#211 opened on Feb 14, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (53 forks)github user discovery
good first issue

Repository metrics

Stars
 (271 stars)
PR merge metrics
 (Avg merge 28d 18h) (4 merged PRs in 30d)

Description

As discussed here: https://github.com/bytecodealliance/StarlingMonkey/pull/200#discussion_r1952578511: It’s unfortunate that we’re only performing encoding to calculate the length of the encoded stream, after which the result is discarded. One possible solution would be to store the encoded output when constructing the FormData.

Contributor guide

Research direction
Explore caching the encoded output during FormData construction to avoid redundant encoding for length calculation. Review the linked PR discussion for context and potential implementation approaches.
Tech stack
cjavascript
Domain
backend
Issue type
Performance
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CJavaScriptFormData API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60