B
Bethe Tomasek
Guest
From time to time we all feel like we need more REST. It’s hectic out there… Should You Implement REST for your Interfaces? Over 70% of Public API’s are based on REST (Representational State Transfer) – Twitter, Facebook, Google, Salesforce, YouTube, etc. are using REST. Why? Easy to understand Uses HTTP & CRUD operations – simple to write & document Easy for other developers to understand & write services against Requires less bandwidth and thus is usually much faster than SOAP. Stateless and not verbose, for better performance & scalability. Most web and mobile applications today use RESTful services due to the light requirements on bandwidth. OpenEdge REST supports JSON, a standardized method for consuming API payloads that provides better support for connection with JavaScript and browsers . Secure – it benefits from Spring Security Framework - best in the industry for security standards Want to try it out? 11.5 Evaluation (will soon be 11.6) - select OpenEdge Ricardo Perdigao Webinar – showing how to expose REST via the Pacific Appserver and taking it a step further to use that service with the Kendo UI. 2015 PUG Challenge Presentations – REST for any application – Matt Baker, The World is your Oyster – Calling REST from the 4GL – Peter Judge Introduction to REST & Creating a Dynamic OE REST Service – Dustin Grau REST Documentation here for more detailed information.
Continue reading...
Continue reading...