-
Notifications
You must be signed in to change notification settings - Fork 247
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
refactor sesion data store module #314
Conversation
1. remove WriteDataProcessor: avoid creating unnecessary objects 2. standardize the use of generic types to avoid code warnings
1. remove WriteDataProcessor: avoid creating unnecessary objects 2. standardize the use of generic types to avoid code warnings
本次pr修改的类文件比较多,其中session上的存储结构的修改也比较大,是否可以在issue补充一些修改后的存储结构的设计考量,对象关系图等。这样对cr人会比较友好。 |
|
@Override | ||
public Pair<Boolean, T> putIfAbsent(T storeData) { | ||
String dataInfoId = storeData.getDataInfoId(); | ||
ClientsGroup<T> clientsGroup = groups.get(dataInfoId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这里可以直接使用computeIfAbsent()?不用自己做两次 == null的判断。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
已修改
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fix: