Yes this is going to be a very open, generic discussion: Do you agree or disagree with the following statement? Why?
SOAP web services are losing favour to REST-based web services. If I were to deploy an OERA application on the web today, I would use REST to interact with the AppServers.
Please feel free to take this in any direction you like.
Paul
Agree with the second part (would use REST). Not sure about the first statement.
There are more clients (incl. web browser) that can talk REST. SOAP is a PITA on webby/mobile platforms (usually they have javascript support and XML is 3rd-party).
Counter question: would you only expose a REST interface, or would you allow a native ABL AppServer too?
-- peter
Interesting counter question. The answer is both. As I see it, the REST interface is really just a cap on top of the business logic AppServer calls. I.e. it takes some output parameters and JSONifies them. (That's a verb, right?)
Seriously though: yesterday it was SOAP. Today it's REST. Tomorrow it's something else. Only the dot-p's with the business logic stay constant throughout. I don't want to be modifying the main code because of the API any more than I want to modify the main code because of the UI.
Paul
well, rest is the de-facto choice for mobile/web and that is mainly
because json but there is no real standard... not that on web-service
world will be much different but at least there are some basics.
rest also lack meta-data and/or discovery services (the wsdl equivalent).
there is at least one attempt to fix those by odata (odata.org), remains
to be seen if psc will adhere or just go with own 'standard'.
otherwise agreed the business logic should be king, rest (sic) are
technicalities... what is needed though is that business logic catalogue
or 'universe' or meta-data to start exposing it to different
mediums/technologies
[collapse]On 06/05/2014 06:04 PM, Paul Koufalis wrote:
>[collapse] From: Paul Koufalis
> Post: RE: SOAP vs REST
> Posted in: OpenEdge General
> Link: http://community.progress.com/technicalusers/f/26/p/10630/39761.aspx#39761
>
> Interesting counter question. The answer is both. As I see it, the REST interface is really just a cap on top of the business logic AppServer calls. I.e. it takes some output parameters and JSONifies them. (That's a verb, right?)
> Seriously though: yesterday it was SOAP. Today it's REST. Tomorrow it's something else. Only the dot-p's with the business logic stay constant throughout. I don't want to be modifying the main code because of the API any more than I want to modify the main code because of the UI.
> Paul
>
>
> --
> You were sent this email because you opted to receive email notifications when someone created a new thread.
>
> To unsubscribe[collapse] from:
> - ...only this thread, disable notifications at http://community.progress.com/technicalusers/f/26/p/10630/39761.aspx#39761.
> - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No".
>
>
--
m.edu
keep it simple
http://www.ganimede.ro
http://ro.linkedin.com/in/marianedu
medu@ganimede.ro
mobile: +40 740 036 212
skype: marian.edu[/collapse][/collapse][/collapse]