Skip to content
This repository was archived by the owner on Aug 10, 2026. It is now read-only.

[EDX-156] Add realtimeRequestTimeout to ClientOptions - #1465

Merged
tbedford merged 1 commit into
mainfrom
EDX-156-add-realtimeRequestTimeout-to-ClientOptions
Jun 20, 2022
Merged

[EDX-156] Add realtimeRequestTimeout to ClientOptions#1465
tbedford merged 1 commit into
mainfrom
EDX-156-add-realtimeRequestTimeout-to-ClientOptions

Conversation

@lawrence-forooghian

Copy link
Copy Markdown
Contributor

This already exists as a user-configurable ClientOptions property in several of our SDKs:

  • ably-java@7fc1939
  • ably-js@48a66d6 (been configurable there since 1b355bf in 2015)
  • ably-ruby@f5eac15
  • ably-go@32ed667
  • ably-flutter@2fe0059

Furthermore, it seems consistent to allow this timeout to be configured, the same way as the others can be.

This already exists as a user-configurable ClientOptions property in
several of our SDKs:
- ably-java@7fc1939
- ably-js@48a66d6 (been configurable there since 1b355bf in 2015)
- ably-ruby@f5eac15
- ably-go@32ed667
- ably-flutter@2fe0059
Furthermore, it seems consistent to allow this timeout to be configured,
the same way as the others can be.
@lawrence-forooghian
lawrence-forooghian marked this pull request as ready for review June 15, 2022 18:57
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-156-add-r-sqpwwk June 15, 2022 18:57 Inactive
@lawrence-forooghianlawrence-forooghian changed the title Add realtimeRequestTimeout to ClientOptions[EDX-156] Add realtimeRequestTimeout to ClientOptionsJun 15, 2022
lawrence-forooghian added a commit to ably/ably-js that referenced this pull request Jun 15, 2022

@ikbalkayaikbalkaya left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM

@tbedford
tbedford merged commit a8c5c24 into mainJun 20, 2022
@tbedford
tbedford deleted the EDX-156-add-realtimeRequestTimeout-to-ClientOptions branch June 20, 2022 07:12
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@lawrence-forooghian@ikbalkaya@Peter-Maguire@QuintinWillison@maratal@kennethkalmer@tbedford