You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Selection of HTTP protocol version via Smithy traits (e.g., @restXml)
Current service models aren't using these correctly, and some operations actually require HTTP 1 for bidirectional event streaming
For now: error out if there's an operation that doesn't specify HTTP 2 for bidirectional streaming, and customize models for known bad operations to specify HTTP 2
Events marked with @error are terminal; should filter them out of the event stream union and handle them as actual SdkErrors
Make Event Stream recv() errors compatible with other SdkErrors when using the ? operator
Non-HTTP bound protocols like AWS JSON send initial members as a struct embedded in a first event frame
Generate new error type for Event Stream recv() since it's not 1-to-1 with the operation errors
Testing
Record bidirectional traffic against all supported protocols:
restJson1
awsJson1 and awsJson1_1
awsQuery
ec2Query
restXml
Exercise all event stream header types
Exercise all event stream payload types (blob, string, struct, union)
Write replay tests
Test the developer experience when the Event Stream input stream yields an error (where does the error go?)
The text was updated successfully, but these errors were encountered:
http::Response
->operation::Response
refactoring in smithy-http (Refactor middleware to use newoperation::Response
instead ofhttp::Response<SdkBody>
#635)http::Request
@restXml
)@error
are terminal; should filter them out of the event stream union and handle them as actual SdkErrorsrecv()
errors compatible with other SdkErrors when using the?
operatorrecv()
since it's not 1-to-1 with the operation errorsThe text was updated successfully, but these errors were encountered: