这是正确的做法。

通常，常量不会保存在单独的“常量”类中，因为它们是不可发现的。如果常量与当前类相关，那么保留它们有助于下一个开发人员。

总之，以秒为单位的timeout值应该是一个配置设置(从属性文件中读取或像Spring中那样通过注入)，而不是一个常量。

这是正确的做法。

通常，常量不会保存在单独的“常量”类中，因为它们是不可发现的。如果常量与当前类相关，那么保留它们有助于下一个开发人员。

有什么不同

1.

public interface MyGlobalConstants {
    public static final int TIMEOUT_IN_SECS = 25;
}

2.

public class MyGlobalConstants {
    private MyGlobalConstants () {} // Prevents instantiation
    public static final int TIMEOUT_IN_SECS = 25;
}

和使用 MyGlobalConstants。TIMEOUT_IN_SECS，我们需要这个常量。我认为两者是一样的。

我强烈建议不要只使用一个常量类。这在当时看起来是一个好主意，但是当开发人员拒绝记录常量，并且类增长到包含500个以上彼此完全不相关的常量(与应用程序的完全不同方面相关)时，通常会导致常量文件完全不可读。而不是:

If you have access to Java 5+, use enums to define your specific constants for an application area. All parts of the application area should refer to enums, not constant values, for these constants. You may declare an enum similar to how you declare a class. Enums are perhaps the most (and, arguably, only) useful feature of Java 5+. If you have constants that are only valid to a particular class or one of its subclasses, declare them as either protected or public and place them on the top class in the hierarchy. This way, the subclasses can access these constant values (and if other classes access them via public, the constants aren't only valid to a particular class...which means that the external classes using this constant may be too tightly coupled to the class containing the constant) If you have an interface with behavior defined, but returned values or argument values should be particular, it is perfectly acceptible to define constants on that interface so that other implementors will have access to them. However, avoid creating an interface just to hold constants: it can become just as bad as a class created just to hold constants.

静态final是我的偏好，我只使用enum如果项目确实是可枚举的。