Struct trust_dns_proto::rr::rdata::hinfo::HINFO[][src]

pub struct HINFO { /* fields omitted */ }

RFC 1035, DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION, November 1987

3.3.2. HINFO RDATA format

    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    /                      CPU                      /
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    /                       OS                      /
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

where:

CPU             A <character-string> which specifies the CPU type.

OS              A <character-string> which specifies the operating
                system type.

Standard values for CPU and OS can be found in [RFC-1010].

HINFO records are used to acquire general information about a host.  The
main use is for protocols such as FTP that can use special procedures
when talking between machines or operating systems of the same type.

Implementations

impl HINFO[src]

pub fn new(cpu: String, os: String) -> HINFO[src]

Creates a new HINFO record data.

Arguments

  • cpu - A which specifies the CPU type.
  • os - A which specifies the operating system type.

Return value

The new HINFO record data.

pub fn from_bytes(cpu: Box<[u8]>, os: Box<[u8]>) -> HINFO[src]

Creates a new HINFO record data from bytes. Allows creating binary record data.

Arguments

  • cpu - A which specifies the CPU type.
  • os - A which specifies the operating system type.

Return value

The new HINFO record data.

pub fn cpu(&self) -> &[u8][src]

A which specifies the CPU type.

pub fn os(&self) -> &[u8][src]

A which specifies the operating system type.

Trait Implementations

impl Clone for HINFO[src]

impl Debug for HINFO[src]

impl Display for HINFO[src]

RFC 1033, DOMAIN OPERATIONS GUIDE, November 1987

HINFO (Host Info)

           <host>   [<ttl>] [<class>]   HINFO   <hardware>   <software>

   The HINFO record gives information about a particular host.  The data
   is two strings separated by whitespace.  The first string is a
   hardware description and the second is software.  The hardware is
   usually a manufacturer name followed by a dash and model designation.
   The software string is usually the name of the operating system.

   Official HINFO types can be found in the latest Assigned Numbers RFC,
   the latest of which is RFC-1010.  The Hardware type is called the
   Machine name and the Software type is called the System name.

   Some sample HINFO records:

           SRI-NIC.ARPA.           HINFO   DEC-2060 TOPS20
           UCBARPA.Berkeley.EDU.   HINFO   VAX-11/780 UNIX

impl Eq for HINFO[src]

impl Hash for HINFO[src]

impl PartialEq<HINFO> for HINFO[src]

impl StructuralEq for HINFO[src]

impl StructuralPartialEq for HINFO[src]

Auto Trait Implementations

impl RefUnwindSafe for HINFO

impl Send for HINFO

impl Sync for HINFO

impl Unpin for HINFO

impl UnwindSafe for HINFO

Blanket Implementations

impl<T> Any for T where
    T: 'static + ?Sized
[src]

impl<T> Borrow<T> for T where
    T: ?Sized
[src]

impl<T> BorrowMut<T> for T where
    T: ?Sized
[src]

impl<T> From<T> for T[src]

impl<T, U> Into<U> for T where
    U: From<T>, 
[src]

impl<T> ToOwned for T where
    T: Clone
[src]

type Owned = T

The resulting type after obtaining ownership.

impl<T> ToString for T where
    T: Display + ?Sized
[src]

impl<T, U> TryFrom<U> for T where
    U: Into<T>, 
[src]

type Error = Infallible

The type returned in the event of a conversion error.

impl<T, U> TryInto<U> for T where
    U: TryFrom<T>, 
[src]

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.

impl<V, T> VZip<V> for T where
    V: MultiLane<T>,