Skip to content

Conversation

@peter-quix
Copy link
Contributor

@peter-quix peter-quix commented May 21, 2024

Description

Quixstreams <1 had support specific binary parameters, however in quixstreams 2.x messages were designed to be less strict in schema. With that, Binary messages are possible if serialization is provided and don't need special handling. In some deprecated Quix APIs there was support for these parameters but that support is now removed.

Review

It is only deletion and mostly on pages with warning of it being outdated anyway. I left the property in for samples that specifically worked with it but all are outdated anyway.

Quixstreams <1 had support specific binary parameters, however in quixstreams 2.x messages were designed to be less strict in schema.
With that, Binary messages are possible if serialization is provided and don't need special handling.
In some deprecated Quix APIs there was support for these parameters but it is no longer present either.
@github-actions
Copy link

github-actions bot commented May 21, 2024

Docs preview site available at https://quixdocsdev.blob.core.windows.net/prdev/index.html

@peter-quix peter-quix changed the base branch from main to dev May 21, 2024 08:50
@tbedford tbedford self-requested a review May 21, 2024 08:52
Copy link
Contributor

@tbedford tbedford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks!

@tbedford tbedford merged commit 1842384 into dev May 21, 2024
@tbedford tbedford deleted the chore/58600 branch May 21, 2024 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants