dotnet / dotnet/aspnetcore

Components.AI: Support scalable attachment transfer, progress, and cancellation

Open
#68,412 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: L feature-blazor-builtin-components Priority:1
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is your feature request related to a problem? Please describe the problem.

Files are fully buffered into `byte[]` and emitted as base64 data URIs, which can cross Blazor Server circuits multiple times and cannot report progress or cancel per attachment.

### Describe the solution you'd like

Provide a streaming upload or application-owned URI/reference path, expose upload progress, and support per-attachment cancellation without requiring all content to be buffered in component memory.

### Additional context

Leaf task for #68227 requirements D6-D7.

Contributor guide

Open the contributing guide

Research direction

Start by reading parent issue #68227, especially requirements D6-D7, then trace the Components.AI attachment-transfer implementation responsible for buffering files and emitting base64 data URIs. Define the supported streaming or application-owned reference path, progress reporting, and per-attachment cancellation behavior; done means attachments no longer require full component-memory buffering and all three capabilities are specified and covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.