Download the PHP package zfcampus/zf-rpc without Composer
On this page you can find all versions of the php package zfcampus/zf-rpc. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zfcampus/zf-rpc
More information about zfcampus/zf-rpc
Files in zfcampus/zf-rpc
Package zf-rpc
Short Description ZF2 Module for simplifying the creation of RPC services
License BSD-3-Clause
Homepage http://apigility.org/
Informations about the package zf-rpc
ZF RPC
Repository abandoned 2019-12-31
This repository has moved to laminas-api-tools/api-tools-rpc.
Introduction
Module for implementing RPC web services in Zend Framework.
Enables:
- defining controllers as PHP callables.
- creating a whitelist of HTTP request methods; requests outside the whitelist will return a
405 Method Not Allowed
response with anAllow
header indicating allowed methods.
Requirements
Please see the composer.json file.
Installation
Run the following composer
command:
Alternately, manually add the following to your composer.json
, in the require
section:
And then run composer update
to ensure the module is installed.
Finally, add the module name to your project's config/application.config.php
under the modules
key:
zf-component-installer
If you use zf-component-installer, that plugin will install zf-rpc as a module for you.
Configuration
User Configuration
This module uses the top-level configuration key of zf-rpc
.
Key: Controller Service Name
The zf-rpc
module uses a mapping between controller service names with the values being an array
of information that determine how the RPC style controller will behave. The key should be a
controller service name that also matches a controller service name assigned to a route in the
router
configuration.
Inside this key, the following sub-keys are required:
http_methods
: for configuring what methods this RPC service controller can respond to. This also is used for populating theAllow
response header for this service.route_name
: for linking back to a particular route. This is especially useful when RPC routes need to build links as part of their response.callable
(optional): utilized to specify a callable that will be invoked at dispatch time. At dispatch time, these callables are typically wrapped in an instance ofZF\Rpc\RpcController
, which is a dispatchable action controller.
Example:
System Configuration
The following configuration ensures this module operates properly in the context of a ZF2 application:
ZF2 Events
Listeners
ZF\Rpc\OptionsListener
This listeners is registered to the MvcEvent::EVENT_ROUTE
event with a priority of -100
. It is
responsible for ensuring the HTTP response to an OPTIONS
request for the given RPC service
includes the properly configured and allowed HTTP methods in the Allow
header. This uses the
configuration from the http_methods
key of the zf-rpc
service configuration for the matching
service. Additionally, it verifies if the incoming request method is in the configured
http_methods
for the RPC service, and, if not, returns a 405 Method Not Allowed
response with a
populated Allow
header.
ZF2 Services
Models
ZF\Rpc\ParameterMatcher
This particular model is used and is useful for taking a callable and a set of named parameters, and determining which ones can be used as arguments to the callable.
Controller
ZF\Rpc\RpcController
This controller is used to wrap a callable registered as an RPC service in order to make it a ZF2 dispatchable.
All versions of zf-rpc with dependencies
zendframework/zend-eventmanager Version ^2.6.3 || ^3.0.1
zendframework/zend-http Version ^2.5.4
zendframework/zend-mvc Version ^2.7.15 || ^3.0.2
zendframework/zend-servicemanager Version ^2.7.6 || ^3.1
zendframework/zend-stdlib Version ^2.7.7 || ^3.0.1
zendframework/zend-view Version ^2.8.1
zfcampus/zf-api-problem Version ^1.2.1
zfcampus/zf-content-negotiation Version ^1.2.1