-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
[suggestion] Seperate Constants.java into some SubConstants Class #3137
Comments
@cvictory |
@CrazyHZM pls. take a look at #4017. I've finished step1.
Let me know if it's reasonable, and which part will you claim for step2. I will start from common: // BEGIN common
public static final String DUBBO = "dubbo";
...
public static final int MAX_PROXY_COUNT = 65535;
// END common |
@beiwei30 |
will you do it based on the current pull request, or wait until it's merged? |
Wait until after being merged |
FYI, the first new constant class I created is: org.apache.dubbo.common.constants.CommonConstants |
I created |
I think we can now move to step3. |
I will start modifying the remoting later. |
so, now we should move to step4, start to review any constants suitable to move back to its own module. for example, in RPCConstants: // BEGIN dubbo-rpc-rest
String KEEP_ALIVE_KEY = "keepalive";
boolean DEFAULT_KEEP_ALIVE = true;
String EXTENSION_KEY = "extension";
// END dubbo-rpc-rest |
Add comments first or move directly? |
if you are pretty sure it should be move into individual module, just do it, and let's review :) |
ok,I will start to review remoting part. |
@CrazyHZM FYI, I am on remoting. |
@beiwei30 |
You can continue to work at this in dubbo-2.7.3 |
Currently we manage out constants values in org.apache.dubbo.common.Constants.java.
This class is very bloated and this structure is not well enough. Maybe we should categorize such constants into groups. In this way , we can add some XxxConstants, such as RegistryConstants,ConfigCenterConstants etc. It'd be better if it is split by module of dubbo-core.
The text was updated successfully, but these errors were encountered: