Skip to content
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.

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

decide how to handle workerId,request key initialization #57

Closed
vkkhare opened this issue Mar 5, 2020 · 0 comments
Closed

decide how to handle workerId,request key initialization #57

vkkhare opened this issue Mar 5, 2020 · 0 comments
Labels
code organisation experimental Type: New Feature ➕ Introduction of a completely new addition to the codebase
Projects

Comments

@vkkhare
Copy link
Member

vkkhare commented Mar 5, 2020

We want to explore the possibility of not using isInitialized and how much added advantage it will bring with it.

@vkkhare vkkhare added code organisation Type: New Feature ➕ Introduction of a completely new addition to the codebase experimental labels Mar 5, 2020
@vkkhare vkkhare added this to To do in KotlinSyft via automation Mar 5, 2020
@vkkhare vkkhare closed this as completed Mar 29, 2020
KotlinSyft automation moved this from To do to Done Mar 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code organisation experimental Type: New Feature ➕ Introduction of a completely new addition to the codebase
Projects
KotlinSyft
  
Done
Development

No branches or pull requests

1 participant