Struct ResolvedService

#[non_exhaustive]
pub struct ResolvedService {
    pub ty_domain: String,
    pub sub_ty_domain: Option<String>,
    pub fullname: String,
    pub host: String,
    pub port: u16,
    pub addresses: HashSet<IpAddr>,
    pub txt_properties: TxtProperties,
}

Represents a resolved service as a plain data struct. This is from a client (i.e. querier) point of view.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

ty_domain: String

Service type and domain. For example, “_http._tcp.local.”

sub_ty_domain: Option<String>

Optional service subtype and domain.

See RFC6763 section 7.1 about “Subtypes”: https://datatracker.ietf.org/doc/html/rfc6763#section-7.1 For example, “_printer._sub._http._tcp.local.”

fullname: String

Full name of the service. For example, “my-service._http._tcp.local.”

host: String

Host name of the service. For example, “my-server1.local.”

port: u16

Port of the service. I.e. TCP or UDP port.

addresses: HashSet<IpAddr>

Addresses of the service. IPv4 or IPv6 addresses.

txt_properties: TxtProperties

Properties of the service, decoded from TXT record.

Implementations

impl ResolvedService

pub fn is_valid(&self) -> bool

Returns true if the service data is valid, i.e. ready to be used.