mirror of
https://github.com/google/nomulus.git
synced 2025-04-30 03:57:51 +02:00
c458c05801
The dark lord Gosling designed the Java package naming system so that ownership flows from the DNS system. Since we own the domain name registry.google, it seems only appropriate that we should use google.registry as our package name.
47 lines
2 KiB
Java
47 lines
2 KiB
Java
// Copyright 2016 The Domain Registry Authors. All Rights Reserved.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
|
|
package google.registry.model.common;
|
|
|
|
import com.googlecode.objectify.Key;
|
|
import com.googlecode.objectify.annotation.Entity;
|
|
import com.googlecode.objectify.annotation.Id;
|
|
|
|
import google.registry.model.BackupGroupRoot;
|
|
|
|
/**
|
|
* The root key for the entity group which is known as the cross-tld entity group for historical
|
|
* reasons.
|
|
*
|
|
* <p>This exists as a storage place for common configuration options and global settings that
|
|
* aren't updated too frequently. Entities in this entity group are usually cached upon load. The
|
|
* reason this common entity group exists is because it enables strongly consistent queries and
|
|
* updates across this seldomly updated data. This shared entity group also helps cut down on
|
|
* a potential ballooning in the number of entity groups enlisted in transactions.
|
|
*
|
|
* <p>Historically, each TLD used to have a separate namespace, and all entities for a TLD were in
|
|
* a single EntityGroupRoot for that TLD. Hence why there was a "cross-tld" entity group -- it was
|
|
* the entity group for the single namespace where global data applicable for all TLDs lived.
|
|
*/
|
|
@Entity
|
|
public class EntityGroupRoot extends BackupGroupRoot {
|
|
|
|
@Id
|
|
private String id;
|
|
|
|
/** The root key for cross-tld resources such as registrars. */
|
|
public static final Key<EntityGroupRoot> getCrossTldKey() {
|
|
return Key.create(EntityGroupRoot.class, "cross-tld");
|
|
}
|
|
}
|