Another example is REST using MQSeries in a stateless flow. 1. The content format is a black block, often a terse/Cobol/C structure, not XML or HTML 2. It is self contained, so if there is a business transaction in several parts( eg signon, query, take action) the request parts can go to any available server (which may be workload balanced). Each individual flow is self contained, there is no state saved in the back end server(s). For example your name and address may be sent in each flow.
With a stateful transaction, the request has to go back to the same server to complete the work. The backend knows the status, so the data flow is just changes in state. Having to parse XML etc is relatively expensive, hence the advantages of terse/Cobol/C structure format when you are doing 1,000 transactions a second. Colin On Fri, 3 Jan 2025 at 21:03, Rupert Reynolds <rreyno...@cix.co.uk> wrote: > It doesn't even have to be http(s), just a client-server setup, although > these days of course it generally is https. > > I'd say it's the details that make it truly RESTful or not, and I think > Dylan Beattie's presentation I mentioned makes a good job of explaining > those details. > > Roops > > On Sun, 22 Dec 2024, 07:32 Mike Beer, <m...@beer.at> wrote: > > > REST is just a series of HTTP or preferably HTTPS calls. > > Usually you have to register and you will have some kind of access code. > > In the first call this access information is transformed into a session > > token that must be used for any further transaction. > > > > The data returned is very often in JSON, but could also be XML. > > > > The session token may expire and for longer transactions it must > therefore > > be renewed. > > > > REST-calls can be made directly or can be part of a call-back service > -then > > the URL of the function has to be registered as well. > > > > Here is a summary of the differences between SOAP and REST: > > https://smartbear.com/blog/soap-vs-rest-whats-the-difference/ > > > > Best regards > > Mike > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > > Of > > Binyamin Dissen > > Sent: Samstag, 21. Dezember 2024 20:53 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: REXX and RESTAPI calls > > > > I have been looking at REST and do not see how it is different than a set > > of > > HTTP transactions. > > > > What am I missing? > > > > On Wed, 18 Dec 2024 19:04:56 +0000 "Shumate, Scott" > > <00000752f95efdcf-dmarc-requ...@listserv.ua.edu> wrote: > > > > :>Truist Data Risk Classification: [-Public-] > > > > :>Does anyone have any experience with REXX making a REST API call to > > service now? If so, could you point me in the right direction? > > > > -- > > Binyamin Dissen <bdis...@dissensoftware.com> > http://www.dissensoftware.com > > > > Director, Dissen Software, Bar & Grill - Israel > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email > > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
