RE: XMLSERVICE

Yes, the purists might say it's probably not true REST, but to me it fits the concept of almost REST just fine :-)

Constructing and deconstructing the XML is the only minor pain.

I laugh because I have been doing REST for years with CGI and ASP.NET before it was called REST :-)

Henrik has volunteered to put a JSON layer on it, so we may not have to..............

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: Wed, 25 Jan 2012 15:31:53 -0500
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: XMLSERVICE


On Jan 25, 2012, at 2:19 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

Brian any way to return JSON data ?

I'm not Brian but ...

Answer right now is no. The request packet has to come in as XML, and the response is the same.

The way it handles the parameters as one XML packet has resulted in my engaging in a debate with staff at one client who claimed it couldn't be ca;ed a REST service because it required XML and didn't behave lile a "normal" REST service. My recent investigations have convinced me that there is no such thing as "conventional" REST but ...

If nobody else gets round to it I might try and do some work in the future on a JSON request/response. XMLSERVICE is incredibly flexible, but that costs and I can't help but feeling that a way of "registering" a particular program's parameter set with it would speed it up and allow a more conventional REST usage - plus of course returning JSON result sets (or whatever is flavor du jour next month).

Jon Paris

www.partner400.com
www.SystemiDeveloper.com