In the case of XMLCGI, the XML appears to get passed as a parm value as part of the query string after the ?
Ex:
http://1.1.1.1/cgi-bin/xmlcgi?parm1=val1&parm2=val2 etc....
That's how I've been doing RESTlike programming for over a decade and it works quite well.
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 08:55:30 -0800
from: Rory Hewitt <rory.hewitt@xxxxxxxxx>
subject: Re: XMLSERVICE
OK, I'll jump in :)
I think Richard puts it quite well:
To me RESTful is anything where I can pass a formatted URL with parms of
some sort and get data back in XML, JSON or whatever format I desire.
If XMLSERVICE allows you to format the URL such that it contains in itself
the entire definition of the data to be processed, then surely it's
RESTful? Now I don't know what Richard meant here by parms, but if they are
part of the URL (as a QUERY_STRING after a '?'), then do they automatically
disqualify XMLSERVICE as RESTful? What about if they are just part of the
URL - at that point it must surely qualify?
Of course, here we're only talking about GET (and maybe POST) rather than
PUT or DELETE, since XMLSERVICE is a 'retriever', but I'd say that a GET
with parms included as part of the URL is certainly RESTful (as long as the
other bits and pieces such as statelessness are fulfilled).
Just my $0.02...
midrange.com
