Skip to content

Implement support is NamedMap.isReady() #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rlubke opened this issue Apr 30, 2023 · 0 comments
Closed

Implement support is NamedMap.isReady() #64

rlubke opened this issue Apr 30, 2023 · 0 comments
Assignees
@rlubke
Labels
enhancement New feature or request

Comments

@rlubke
Copy link
Member

rlubke commented Apr 30, 2023

14.1.1.2206.5 includes an update to the NamedMap called isReady() returning a boolean.

If the client is connecting to an older proxy and isReady() is called on the client, it should raise an appropriate error stating the operation isn't supported by the current proxy. Either upgrade the proxy or connect to a proxy that supports this operation.
@rlubke rlubke added the enhancement New feature or request label Apr 30, 2023
@rlubke rlubke self-assigned this Aug 18, 2023
rlubke added a commit that referenced this issue Aug 18, 2023
@rlubke
Fix #64 Implement support is NamedMap.isReady()
c5c4330
@rlubke rlubke closed this as completed in 1ec0ae4 Aug 18, 2023
rlubke added a commit that referenced this issue Aug 21, 2023
@rlubke
Fix #64 Implement support is NamedMap.isReady()
3637c25 
 - refactoring checkpoint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rlubke rlubke

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rlubke