-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.x.x - Wrap InboundStream iterator in request body #369
Merged
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1700ffb
Stick NIOAsyncChannel in request body streamer
adam-fowler 25da551
Clean up, remove task group in HTTPChannelHandler
adam-fowler ed9fe38
Add more checking in HBStreamedRequestBody.AsyncIterator.next
adam-fowler 560c57f
Fix benchmarks
adam-fowler 9b2ff87
Fix finished request flush
adam-fowler c569af7
don't use function to flush body parts
adam-fowler 0dca77a
Add support for creating stream from byteBuffer, only allow one itera…
adam-fowler f7089bb
2.x.x - Use AnyAsyncSequence and creating request body streams (#373)
adam-fowler File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
//===----------------------------------------------------------------------===// | ||
// | ||
// This source file is part of the Hummingbird server framework project | ||
// | ||
// Copyright (c) 2024 the Hummingbird authors | ||
// Licensed under Apache License v2.0 | ||
// | ||
// See LICENSE.txt for license information | ||
// See hummingbird/CONTRIBUTORS.txt for the list of Hummingbird authors | ||
// | ||
// SPDX-License-Identifier: Apache-2.0 | ||
// | ||
//===----------------------------------------------------------------------===// | ||
|
||
//===----------------------------------------------------------------------===// | ||
// | ||
// This source file is part of the SwiftNIO open source project | ||
// | ||
// Copyright (c) 2021-2022 Apple Inc. and the SwiftNIO project authors | ||
// Licensed under Apache License v2.0 | ||
// | ||
// See LICENSE.txt for license information | ||
// See CONTRIBUTORS.txt for the list of SwiftNIO project authors | ||
// | ||
// SPDX-License-Identifier: Apache-2.0 | ||
// | ||
//===----------------------------------------------------------------------===// | ||
|
||
/// ``UnsafeTransfer`` can be used to make non-`Sendable` values `Sendable`. | ||
/// As the name implies, the usage of this is unsafe because it disables the sendable checking of the compiler. | ||
/// It can be used similar to `@unsafe Sendable` but for values instead of types. | ||
@usableFromInline | ||
struct UnsafeTransfer<Wrapped> { | ||
@usableFromInline | ||
var wrappedValue: Wrapped | ||
|
||
@inlinable | ||
init(_ wrappedValue: Wrapped) { | ||
self.wrappedValue = wrappedValue | ||
} | ||
} | ||
|
||
extension UnsafeTransfer: @unchecked Sendable {} | ||
|
||
extension UnsafeTransfer: Equatable where Wrapped: Equatable {} | ||
extension UnsafeTransfer: Hashable where Wrapped: Hashable {} | ||
|
||
/// ``UnsafeMutableTransferBox`` can be used to make non-`Sendable` values `Sendable` and mutable. | ||
/// It can be used to capture local mutable values in a `@Sendable` closure and mutate them from within the closure. | ||
/// As the name implies, the usage of this is unsafe because it disables the sendable checking of the compiler and does not add any synchronisation. | ||
@usableFromInline | ||
final class UnsafeMutableTransferBox<Wrapped> { | ||
@usableFromInline | ||
var wrappedValue: Wrapped | ||
|
||
@inlinable | ||
init(_ wrappedValue: Wrapped) { | ||
self.wrappedValue = wrappedValue | ||
} | ||
} | ||
|
||
extension UnsafeMutableTransferBox: @unchecked Sendable {} |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should prevent exposing this type, as we're locking ourselves in a corner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point we are going to have to expose a public way to create a
HBRequestBody
that is initialised with a stream of data and at that time we'll have to expose the internal type to avoid having to do type conversions.