Skip to content

Commit 07c259a

Browse files
Remove streams comment
1 parent af98f28 commit 07c259a

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

WEB-INTEGRATION.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -359,12 +359,9 @@ In general, the context that should be used is the one that matches the data
359359
flow through the algorithms ([see the section on implicit propagation
360360
below](#implicit-context-propagation)).
361361

362-
<!-- Streams are largely defined on top of promises, and can be easily
363-
reimplemented in userland by copying the spec step-by-step. Likely this
364-
described propagation already properly comes out of that? -->
365-
366-
> TODO: Piping is largely implementation-defined. We should figure out some
367-
> context propagation constraints.
362+
> TODO: Piping is largely implementation-defined. We will need to explicitly
363+
> define how propagation works there, rather than relying on the streams
364+
> usage of promises, to ensure interoperability.
368365
369366
> TODO: If a stream gets transferred to a different agent, any cross-agent
370367
> interactions will have to use the empty context. What if you round-trip a

0 commit comments

Comments
 (0)