You may have worked with Zend Feed as a standalone component. I don’t know whether you have integrated Zend framework Feed with Guzzle as Http Client.
This post is inspired by Matthew Weier O’Phinney, who have mentioned the same on github.
Our composer.json looks
1 2 3 4 5 6 7 8 9 10 11 12 { "require": { "guzzlehttp/guzzle": "~5.2", "zendframework/zend-feed": "~2.3", "zendframework/zend-servicemanager": "~2.3" }, "autoload": { "psr-0": { "": "src/" } } } Zen\Feed\Reader\Reader have a method importRemoteFeed which accepts an instance of Zend\Feed\Reader\Http\ClientInterface.
This post is a thrive to learn, and not to show anyone is incorrect. Feel free to share your thoughts.
Lukas Kahwe Smith was having a nice post RESTing with Symfony2
Quoting a few words from the post on REST
DELETE and 404 # I started my talk on RESTing with Symfony2 with an introduction to REST itself. On slide 7 of my talk I explained the concept of “safe” and “idempotent” HTTP methods. Many people were surprised when I explained that DELETE should be idempotent, meaning that sending a DELETE request to a resource that has been removed should infact not return a 404.
The Aura.Http package provide you the tool to build and send request and response.
Instantiation: # The easiest way is
1 2 3 <?php $http = require 'path/to/Aura.Http/scripts/instance.php'; What it gives you is an object of Aura\Http\Manager. If you want to create manually you can look into the instance.php
Building your Response # Probably you may not have bothered too much on building the http response either the framework does it for you, or until you need to send the correct response.