Re: [fw-webservices] Problem with Zend_XmlRpc_Client

-- swilhelm <steve@studio831.com> wrote
(on Wednesday, 04 February 2009, 10:56 AM -0800):
> Thanks. I'll squirrel away this tidbit for future use.
>
> Since I am already familiar with the MVC model, I think using it turned out
> to be easier. I understand it will be slower. How much slower is it if I
> use a Zend_Controller_Router_Route_Static route to all the API calls?

The problem isn't routing -- routing is actually very fast. The problem
is that there are many layers of objects used when using the MVC --
front controller, request object, response object, plugins (error
handler plugin is registered by default), router (and individual route
objects), dispatcher, action helpers (view renderer is registered by
default; others on demand), action controller, view object, view
helpers... If all you really require is a service end point, a script
that simply instantiates the server and handles the request is much
faster; the one time I benchmarked it, typical requests were answered 10
- 20 times faster than MVC requests.

> btw, "$this->_helper->json($data);" is my favorite of line of code this
> week.

:)

> Matthew Weier O'Phinney-3 wrote:
> >
> > -- swilhelm <steve@studio831.com> wrote
> > (on Wednesday, 04 February 2009, 09:25 AM -0800):
> >> There were two specific things I wanted to do I found difficult with
> >> Zend_REST and Zend_XmlRPpc:
> >>
> >> I wanted to secure the set method by having clients pass authentication
> >> credientials with each call or have a login call that returned a session
> >> id
> >> and have subsequent calls pass id. Acl would be perfect for this, but
> >> didn't
> >> see any easy way to use it with either REST or XmlRpc.
> >
> > This is actually easy to do by extending the Zend_XmlRpc_Request object.
> > What you can do in these cases is check to see if the method is for
> > "logging in", and if not, strip the first or last parameter from the
> > passed parameters and check it against the authentication session. As an
> > example:
> >
> > class My_XmlRpc_Request extends Zend_XmlRpc_Request_Http
> > {
> > public function __construct()
> > {
> > parent::__construct();
> >
> > if ($this->getMethod() != 'login') {
> > $params = $this->getParams();
> > $token = array_shift($params);
> > $this->setParams($params);
> >
> > // Verify the token, and then add it to the registry...
> > Zend_Registry::set('token', $token);
> > }
> > }
> > }
> >
> > Notice that I grab the parameters, remove an element, and then re-set
> > them without that element -- that's the only magic that needs to happen.
> > How you do the authentication or ACLs after that is up to you.
> >
> > Then, in the endpoint script where the XML-RPC server is created, also
> > instantiate this class and add it to the server:
> >
> > $request = new My_XmlRpc_Request();
> > $server->setRequest($request);
> >
> >> One set call where the body of the POST was an existing XML format
> >> dictated
> >> by an existing client. In the wee hours of the morning, couldn't figure
> >> out
> >> how to get REST or Xml Rpc to accept a XML post body from a client.
> >
> > Again, what you want to do here is to extend Zend_XmlRpc_Request (or the
> > _Http variant); in ZF's XML-RPC implementation, that's where we do the
> > parsing of the request into the requisite method and parameters. If the
> > response also needs to be in a specific format, extend
> > Zend_XmlRpc_Response (or the _Http variant), and override the saveXML()
> > method to build the appropriate response payload. Just like with the
> > request, you need to add the response object to the server prior to
> > handling the request.
> >
> > These techniques work for all the server variants, by the way -- you can
> > do the same with the REST or JSON servers.
> >
> >> Finally, had some Action control helpers for handling MySQL access and
> >> Logging that I just found easier to access using standard Controller
> >> behavior.
> >>
> >> If you have an example of REST or XmlRpc client and server that has
> >> authenticated set call with a large JSON or XML data parameter from
> >> client,
> >> I should would appreciate seeing it.
> >>
> >> Thanks in advance.
> >>
> >> - Steve W.
> >>
> >>
> >> Matthew Weier O'Phinney-3 wrote:
> >> >
> >> > -- swilhelm <steve@studio831.com> wrote
> >> > (on Saturday, 31 January 2009, 10:37 PM -0800):
> >> >> I just spent several frustrating hours trying to set up a Web service
> >> >> using
> >> >> first Zend_REST_Server and then Zend_XmlRpc_Server. Both turned out to
> >> be
> >> >> to
> >> >> limiting.
> >> >
> >> > Could you explain what you found limiting in the XML-RPC
> >> implementation?
> >> > I'd be curious to what your issues may have been, and what improvements
> >> > we might be able to make.
> >> >
> >> >> Eventually, I took Matthew O'Phinney's advice from
> >> >> http://www.nabble.com/Our-REST-implementation-td10834932s16154.html
> >> this
> >> >> discussion and used the standard MVC mechanisms and had the views
> >> >> returned
> >> >> well formatted XML data (I do eventually intend to leverage
> >> ContextSwitch
> >> >> capability).
> >> >>
> >> >> - Steve W.
> >> >>
> >> >>
> >> >> anz_nabble wrote:
> >> >> >
> >> >> > Can anyone explain how to develop a simple webservice using xml rpc.
> >> >> > I had done many searches and didn't find a useful one. I need to
> >> know
> >> >> > which files are placed in which locations
> >> >> >
> >> >> > Any good tutorial?
> >> >
> >> > --
> >> > Matthew Weier O'Phinney
> >> > Software Architect | matthew@zend.com
> >> > Zend Framework | http://framework.zend.com/
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Problem-with-Zend_XmlRpc_Client-tp21598685p21835239.html
> >> Sent from the Zend Web Services mailing list archive at Nabble.com.
> >>
> >
> > --
> > Matthew Weier O'Phinney
> > Software Architect | matthew@zend.com
> > Zend Framework | http://framework.zend.com/
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Problem-with-Zend_XmlRpc_Client-tp21598685p21837039.html
> Sent from the Zend Web Services mailing list archive at Nabble.com.
>

--
Matthew Weier O'Phinney
Software Architect | matthew@zend.com
Zend Framework | http://framework.zend.com/