Lines Matching refs:an
44 Each of these configuration components is referred to as an 'entity'.
59 External Network Modifiers (ENMs): units that specify an external service
60 or executable that modifies the network configuration. Properties of an
61 ENM include an FMRI or Start and Stop exec strings, an optional environment
62 which will be activated when the ENM is started, an activation type specifying
63 when the ENM should be started (e.g. on user input, dependent on an NCU--
96 interface state or the removal of an interface.
108 Access to entities is attained via an entity-specific handle. These
111 nwam_<entity>_create() will create an in-memory representation of the
118 All changes made after binding a handle to an entity, and prior to calling
120 entity. nwam_<entity>_commit() updates persistent storage in an all-or-none
124 To destroy an entity in persistent storage, nwam_<entity>_destroy() is
129 To summarize, the pattern of interactions with an entity is
140 changes). However, it is possible that a _read() will retrieve an
141 outdated view of an entity, if after the _read() completes, another
147 Entity validation on an in-memory representation can be explicitly requested
152 and nwam_<entity>_get_prop_value(). These functions require an nwam_value_t as
290 NCUs are manipulated via an nwam_ncu_handle_t.
293 have mutiple values associated with it, which are set or retrieved via an
295 the difference that read/commit/destroy must specify an NCP. Only two
298 the automatic NCP's consituent NCUs will result in an NWAM_ENTITY_READ_ONLY
333 Locations are manipulated via an nwam_loc_handle_t.
335 A loc handle maps to an in-memory representation of a location; operations via
393 ENMs are manipulated via an nwam_enm_handle_t, in a similar manner to
448 Known WLANs are manipulated via an nwam_known_wlan_handle_t, in a similar
503 All functions return an nwam_error_t if they return an error. Possible