mirror of
https://github.com/google/nomulus.git
synced 2025-07-25 03:58:34 +02:00
parent
4399067ddd
commit
a12a716806
119 changed files with 985 additions and 1032 deletions
|
@ -333,8 +333,6 @@ registry codebase:
|
|||
remembering which dates have been processed. For instance, for the RDE
|
||||
export, Cursor entities maintain the date up to which each TLD has been
|
||||
exported.
|
||||
* `DomainApplicationIndex` -- These hold domain applications received during
|
||||
the sunrise period.
|
||||
* `Domain` -- These hold the ICANN domain information.
|
||||
* `DomainRecord` -- These are used during the DNS update process.
|
||||
* `EntityGroupRoot` -- There is only one EntityGroupRoot entity, which serves
|
||||
|
@ -351,7 +349,7 @@ registry codebase:
|
|||
* `HistoryEntry` -- A HistoryEntry is the record of a command which mutated an
|
||||
EPP resource. It serves as the parent of BillingEvents and PollMessages.
|
||||
* `HostRecord` -- These are used during the DNS update process.
|
||||
* `HostResource` -- These hold the ICANN host information.
|
||||
* `Host` -- These hold the ICANN host information.
|
||||
* `Lock` -- Lock entities are used to control access to a shared resource such
|
||||
as an App Engine queue. Under ordinary circumstances, these locks will be
|
||||
cleaned up automatically, and should not accumulate.
|
||||
|
|
|
@ -148,7 +148,7 @@ as follows:
|
|||
sunrise or landrush
|
||||
* `DomainResource`, a domain name allocated following a successful
|
||||
application, or registered during a general availability phase
|
||||
* `HostResource` ([RFC 5732](https://tools.ietf.org/html/rfc5732))
|
||||
* `Host` ([RFC 5732](https://tools.ietf.org/html/rfc5732))
|
||||
* `ContactResource` ([RFC 5733](https://tools.ietf.org/html/rfc5733))
|
||||
|
||||
All `EppResource` entities use a Repository Object Identifier (ROID) as its
|
||||
|
@ -172,9 +172,9 @@ the status of a resource at a given point in time.
|
|||
Foreign key indexes provide a means of loading active instances of `EppResource`
|
||||
objects by their unique IDs:
|
||||
|
||||
* `DomainResource`: fully-qualified domain name
|
||||
* `Domain`: fully-qualified domain name
|
||||
* `ContactResource`: contact id
|
||||
* `HostResource`: fully-qualified host name
|
||||
* `Host`: fully-qualified host name
|
||||
|
||||
Since all `EppResource` entities are indexed on ROID (which is also unique, but
|
||||
not as useful as the resource's name), a `ForeignKeyIndex` provides a way to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue