|Description:||issue adhoc SOURCE protocol requests to an nkp:// Server|
with the following arguments: (for more details on argument passing details see here)
|base||String (unknown)||(no description available)|
|path||String (anything)||(no description available)|
The response representation of this accessor for SOURCE requests is unknown.
This accessor throws no documented exceptions.
To use NKPProtocolRequest accessor you must import the module urn:com:ten60:netkernel:nkp:
nkp:// URI scheme consists of scheme identifier, host and port followed by an arbitrary path
This URI is used to construct an NKP client connection to the NKP server at host:port. The path of the nkp: URI is converted to a generic res:/ request which is issued into the server's NKP host space. [ You can use the active:NKPRequest if you require the full richness of general declarative requests on the server side. ]
If you have an NKP server on host myhost.com at port 10601 and which has an endpoint resolving "res:/some/service" then you can make a one-shot request for this resource with
which becomes on the NKP serverside...
By using the nkps:// scheme you indicate that the endpoint should negotiate TLS encryption of the connection to the NKP server.
You must provide in the client-side address space a resource res:/etc/NKPClientConfig.xml. This contains detailed configuration state for the NKP connection which the nkp:// request will use.
Note the values for host and port in the nkp:// URI will override any settings for these in the configuration. Also specifying nkps:// will always force TLS encryption.
As a bare minimum we recommend that the configuration specifies how to treat server-side requests. The following configuration will explicitly prevent server-side requests into the client address space during the the execution of the nkp:// request...