When using WebSockets, the channel represents the connection. Unlike other protocols that support multiple virtual channels (topics, routing keys, etc.) per connection, WebSockets doesn't support virtual channels or, put it another way, there's only one channel and its characteristics are strongly related to the protocol used for the handshake, i.e., HTTP.
Get JSON SchemaBundle| Identifier | https://schemas.sourcemeta.com/asyncapi/bindings/websockets/0.1.0/channel.json |
|---|---|
| Base Dialect | Draft7 |
| Dialect | http://json-schema.org/draft-07/schema# |
| Health | |
| Size | 0.001933 MB |
This schema has 3 direct dependencies and 3 indirect dependencies.
| Origin | Dependency |
|---|---|
/patternProperties/^x-[\w\d\.\x2d_]+$/$ref | /asyncapi/definitions/3.0.0/specificationextension |
/properties/headers/oneOf/0/$ref | /asyncapi/definitions/3.0.0/schema |
/properties/headers/oneOf/1/$ref | /asyncapi/definitions/3.0.0/reference |
| Indirect | http://json-schema.org/draft-07/schema |
| Indirect | /asyncapi/definitions/3.0.0/externaldocs |
| Indirect | /asyncapi/definitions/3.0.0/referenceobject |
This schema has 3 quality errors.
/properties/bindingVersion/enumenum_to_constAn `enum` of a single value can be expressed as `const`
/properties/bindingVersion/enumenum_with_typeSetting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
/properties/method/enumenum_with_typeSetting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types