pub enum AppUsage {
Normal,
Loopback,
LinkLocal,
NxDomain,
}
Expand description
Application Software:
Are writers of application software expected to make their software recognize these names as special and treat them differently? In what way? (For example, if a human user enters such a name, should the application software reject it with an error message?)
Variants
Normal
Application software SHOULD NOT recognize these names as special, and SHOULD use these names as they would other reverse-mapping names.
Application software SHOULD NOT recognize test names as special, and SHOULD use test names as they would other domain names.
Application software SHOULD NOT recognize example names as special and SHOULD use example names as they would other domain names.
Loopback
Application software MAY recognize localhost names as special, or MAY pass them to name resolution APIs as they would for other domain names.
LinkLocal
Link local, generally for mDNS
NxDomain
Application software MAY recognize “invalid” names as special or MAY pass them to name resolution APIs as they would for other domain names.
Trait Implementations
impl Copy for AppUsage
impl Eq for AppUsage
impl StructuralEq for AppUsage
impl StructuralPartialEq for AppUsage
Auto Trait Implementations
impl RefUnwindSafe for AppUsage
impl Send for AppUsage
impl Sync for AppUsage
impl Unpin for AppUsage
impl UnwindSafe for AppUsage
Blanket Implementations
sourceimpl<T> BorrowMut<T> for T where
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized,
const: unstable · sourcefn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more
sourceimpl<T> ToOwned for T where
T: Clone,
impl<T> ToOwned for T where
T: Clone,
type Owned = T
type Owned = T
The resulting type after obtaining ownership.
sourcefn clone_into(&self, target: &mut T)
fn clone_into(&self, target: &mut T)
toowned_clone_into
)Uses borrowed data to replace owned data, usually by cloning. Read more