×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Nice summary. It simply re-enforces my definition.
My definition is "close enough" for me. I live in the real world, not academia :-)
I will give you this though:
I had to write a chunk of .Net code to format the XML parameters the way I wanted them, so the XMLSERVICE way isn't without its flaws :-)
However if Zend has chosen to adopt it, it's worth a look to anyone following this thread.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 4
date: Fri, 27 Jan 2012 12:43:56 -0600
from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
subject: Re: XMLSERVICE
And now you, Richard, are saying that it's just one more small deviation
of naming the program and parameters in an XML document is okay, and
it's still REST.
GET
http://example.com/cgi-bin/xmlcgi.pgm?db2=*LOCAL&uid=scott&pwd=pasword&ipc=/tmp/inventory&ctl=*sbmjob&xmlin=<...xmlfile
with program definitions, parameters, return types, etc....>
I mean... at what point does it cease being "close enough" to RESTful?
midrange.com
