Struct Support 

pub struct Support { /* private fields */ }

What a registrar said about push, read from the Feature-Caps of a REGISTER response (§8.2).

The interesting question this answers is not “did the registration succeed” — it did, or there would be no response to read. It is “can this registrar actually wake me”, and the two come apart: a registrar that supports some other push service answers 200 and records a perfectly good binding that nothing will ever ring. That failure looks exactly like success from every angle except this one.

Implementations

impl Support

pub fn from_response(response: &Response) -> Self

Read what a REGISTER response said about push (§8.2).

Every Feature-Caps row is read, because a registrar offering several push services says so with several indicators and a client that stopped at the first would miss its own.

pub fn services(&self) -> &[String]

The push notification services the registrar named (§8.2’s sip.pns).

pub fn supports(&self, provider: &str) -> bool

Whether the registrar named this push service.

The question a client has to ask after every registration, and the reason sip.pns exists. false does not mean the registration failed — it means the binding is one nothing will wake, and a client that never asks will sit there believing it is reachable.

Compared case-insensitively: §8.8’s registry values are tokens.

pub fn refreshes_required(&self) -> bool

Whether the registrar asked for binding refreshes even without a push (§8.2’s sip.pnsreg).

pub fn refresh_interval(&self) -> Option<Duration>

How long to leave between those refreshes, when the registrar said a readable number.

None alongside a true Support::refreshes_required means the registrar asked for refreshes without naming an interval this side could read; the lease’s own refresh point still applies.

pub fn purr(&self) -> Option<&str>

The PURR the registrar assigned this binding (§8.2’s sip.pnspurr).

Carried, not acted on. A PURR exists so that a request can be matched to a stored binding without re-deriving it from the pn-* values, and the party that stores bindings is the registrar or the proxy of §5.6 — not a user agent, which has exactly one. sipx therefore reads it, keeps it, and hands it to the application, and does no matching with it; that half arrives with the proxy role or not at all.

pub fn is_empty(&self) -> bool

Whether the registrar said nothing about push at all — every registrar that does not implement RFC 8599, which is not an error and not a refusal.

Trait Implementations

impl Clone for Support

fn clone(&self) -> Support

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Support

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Support

fn default() -> Support

Returns the “default value” for a type.

impl PartialEq for Support

fn eq(&self, other: &Support) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Eq for Support

impl StructuralPartialEq for Support