Add support for retained intents #142
Assignees
Projects
Comments
danielwiehl
added a commit
that referenced
this issue
Nov 7, 2022
Similar to retained messages, retained intents help newly subscribed clients receive the last intent published to a capability immediately upon subscription. closes #142
danielwiehl
added a commit
that referenced
this issue
Nov 7, 2022
Similar to retained messages, retained intents help newly subscribed clients receive the last intent published to a capability immediately upon subscription. closes #142
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send an intent or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send a message or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send a message or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send a message or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send a message or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to send a message or request data. Content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to control how to send a message or request. The content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable or decorating the `IntentClient`. Note that the communication protocol between host and client has NOT changed, i. e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to control how to send a message or request. The content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable or decorating the `IntentClient`. Note that the communication protocol between host and client has NOT changed, i.e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
danielwiehl
added a commit
that referenced
this issue
Nov 8, 2022
Similar to a retained message, a retained intent helps newly subscribed clients receive the last intent published for a capability. The platform supports the sending of retained intents and requests. closes #142 BREAKING CHANGE: The `IntentClient` now uses the same `options` object as the `MessageClient` to control how to send a message or request. The content of the `options` object has not changed, only its name, i.e., migration is only required if assigning it to a typed variable or decorating the `IntentClient`. Note that the communication protocol between host and client has NOT changed, i.e., host and clients can be migrated independently. To migrate: - options for sending an intent was changed from `IntentOptions` to `PublishOptions` (`IntentClient#publish`) - options for requesting data was changed from `IntentOptions` to `RequestOptions` (`IntentClient#request`)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Retained messaging helps late subscribers receive and process messages sent prior to their subscription. The platform supports retained messaging for topic-based communication, but not for intent-based communication and not in request-response communication.
Describe the solution you'd like
The platform supports retained messaging as follows:
The text was updated successfully, but these errors were encountered: