[ новости /+++ | форум | теги | ]

NAME
     fn_ctx_handle_from_initial - return a handle to the  Initial
     Context

SYNOPSIS
     cc [ flag ... ] file ... -lxfn [ library ... ]
     #include <xfn/xfn.h>

     FN_ctx_t *fn_ctx_handle_from_initial(unsigned int authorita-
     tive, FN_status_t *status);

DESCRIPTION
     This operation returns a handle to the caller's Initial Con-
     text.  On successful return, the handle points to  a context
     which meets the specification of  the  XFN  Initial  Context
     (see  fns_initial_context(5)).

     authoritative specifies whether the handle  to  the  context
     returned should be authoritative with respect to information
     the context obtains from the naming service. When  the  flag
     is  non-zero,  subsequent  operations  on  the  context will
     access the most authoritative information.  When  authorita-
     tive  is  0,  the handle to the context returned need not be
     authoritative.

RETURN VALUES
     fn_ctx_handle_from_initial()  returns  a   pointer   to   an
     FN_ctx_t object if the operation succeeds; it returns a NULL
     pointer (0) otherwise.

ERRORS
     fn_ctx_handle_from_initial() sets only the status code  por-
     tion of the status object status.

USAGE
     Authoritativeness is determined by specific naming services.
     For  example,  in a naming service that supports replication
     using a master/slave  model,  the  source  of  authoritative
     information  would come from the master server. In some nam-
     ing systems, bypassing the naming service  cache  may  reach
     servers  which  provide  the most authoritative information.
     The availability of an authoritative context might be  lower
     due  to  the  lower number of servers offering this service.
     For the same reason, it might also  provide  poorer  perfor-
     mance than contexts that need not be authoritative.

     Applications set authoritative to 0 for  typical  day-to-day
     operations.  Applications  only  set authoritative to a non-
     zero value when they require access to the  most  authorita-
     tive  information,  possibly at the expense of lower availa-
     bility and/or poorer performance.

     It is implementation-dependent whether authoritativeness  is
     transferred  from  one context to the next as composite name
     resolution proceeds. Getting an authoritative context handle
     to  the Initial Context means that operations on bindings in
     the Initial Context are processed using the most  authorita-
     tive  information. Contexts referenced implicitly through an
     authoritative Initial Context (for example, through the  use
     of  composite  names)  may  not  necessarily  themselves  be
     authoritative.

ATTRIBUTES
     See attributes (5) for descriptions of the following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | MT-Level                    | MT-Safe                     |
    |_____________________________|_____________________________|


SEE ALSO
     FN_ctx_t(3XFN),   FN_status_t(3XFN),   fn_ctx_get_ref(3XFN),
     fn_ctx_handle_from_ref(3XFN),                     xfn(3XFN),
     xfn_status_codes(3XFN),                       attributes(5),
     fns_initial_context(5)

NOTES
     The implementation of XFN in this Solaris release  is  based
     on  the  X/Open preliminary specification. It is likely that
     there will be minor changes to these interfaces  to  reflect
     changes in the final version of this specification. The next
     minor release of Solaris will offer binary compatibility for
     applications  developed using the current interfaces. As the
     interfaces evolve toward  standardization,  it  is  possible
     that  future  releases  of Solaris will require minor source
     code  changes  to  applications  that  have  been  developed
     against the preliminary specification.

Партнёры:

Хостинг: