NAME | FEATURE SUMMARY | API | ATTRIBUTES
Low overhead, same-site invocation of functions and APIs exported by supervisor actors may be done through use of local access points, or LAPs (see CORE(5FEA)). A LAP is designated and invoked via its LAP descriptor. A LAP descriptor may be directly transmitted by a server to one or more specific client actors, via shared memory or as an argument in another invocation. Alternatively, the LAPBIND feature provides a nameserver from which a LAP descriptor may be requested and obtained indirectly, using a static symbolic name which may be an arbitrary character string. Using the nameserver, a LAP may be exported to any potential client that knows the symbolic name of the LAP (or of the service exported via the LAP).
A server may optionally establish a name binding using svLapBind, and remove a binding using svLapUnbind. A client uses lapResolve to obtain a lap descriptor, given its symbolic name, optionally waiting if the name is not yet available.
The LAPBIND API is summarized in the following table:
Comment
Find a lap descriptor by name.
Bind a name to a lap.
Unbind a lap name.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Interface Stability | Evolving |
NAME | FEATURE SUMMARY | API | ATTRIBUTES