Download the PHP package rds/jrf without Composer
On this page you can find all versions of the php package rds/jrf. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package jrf
Short Description JSON-RPC 2.0 Framework
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package jrf
JSON RPC Framework (JRF)
JRF is a JSON-RPC over HTTP data providing framework. Simple component-based architecture allow you to fast and easy web service developing. From the box (as-is) JRF supports a controller/action factory, input interface (PhpInput by default), and MiddleWare request checking.
SchemaChecker interface allow to hint-and-check incoming params for any method provided by yours application service.
Smart-fault interface is very easy to use. You don't need to care about anything low-level lifecycle catchers and response result builders. Just raise and see =)
Outside of the box, you can create a powerful controller-based application service with controller factory.
Usage example
Just post JSON on it:
Overriding input interface
If php://input is a bad way for you, you can create your own input:
And override default like this:
All done =) Your provider will work fine inside JRF ecosystem.
Create access middleware
In "captain obvious" opinion, all available private service must have access provisioning module. Let's code-in it:
Let's add our middleware into service:
Create custom controller factory
Simple and easy way to create factory - use namespace-based action provider.
Implementation:
Incoming params hinting/checking
For example, json was posted is:
Rules:
- a > 0
- b > 0
- a is INT
- b is INT
- a REQUIRED
- b REQUIRED
Implementation
Configuration container
Configuration Container instantiated Inside JRF constructor method with options passed inside it. To access container JRF provide method named "config", config access examples:
Client usage
Unit Tests
No-HTTP Usage
If that really needed, JRF allow to handle custom input interface without any listeners. By this way JRF is not provide response output. However, if you need to use couple of providers both, you can run service by add $service->listen().
License
Copyright (c) 2014 Rambler&Co
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
