Copyright (c) 2004-2006 Storage Networking Industry Association. All Rights Reserved.
Portions Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
cc [ flag.\|.\|. ] file.\|.\|. -lMPAPI [ library.\|.\|. ] #include <mpapi.h> MP_STATUS MP_RegisterPlugin(MP_WCHAR *pPluginId, MP_CHAR *pFileName);
A pointer to the key name shall be the reversed domain name of the vendor followed by a ".", followed by the vendor-specific name for the plugin that uniquely identifies it.
The full path name of the plugin library.
The MP_RegisterPlugin() function registers a plugin with the common library. The current implementation adds an entry to the /etc/mpapi.conf file.
Unlike some other APIs, this API is implemented entirely in the common library. It must be called before a plugin is invoked by the common library.
This API does not impact dynamically add or change plugins bound to a running library instance. Instead, it causes an application that is currently not using a plugin to access the specified plugin on future calls to the common library. This is generally the behavior expected from dynamically loaded modules.
This API is typically called by a plugin's installation software to inform the common library of the path for the plugin library.
It is not an error to re-register a plugin. However, a plugin has only one registration. The first call to deregister a plugin will deregister it no matter how many calls to register the plugin have been made.
A vendor may register multiple plugins by using separate plugin IDs and filenames.
The pFileName does not exist.
The operation is successful.
MPAPI library configuration file
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE ATTRIBUTE VALUE |
| Interface Stability |
| Standard: ANSI INCITS 412 Multipath Management API |
| MT-Level Safe |
libMPAPI(3LIB), MP_DeregisterPlugin(3MPAPI), mpapi.conf(4), attributes(5)
Multipath Management API Version 1.0