M
Michael Jacobs
Guest
The Mobile project's business entities, by design, exclude access to anything in the HTTP request & response messages. So, you choose REST when your ABL application code requires direct access to the HTTP request/response context, headers, cookies, and character formatted body contents. For all other cases I think the Mobile project's business entities are the best fit. A REST service, in either a REST or Mobile project, allows you to map any HTTP artifact to procedure/class-method parameters. The penalty you pay for having accessing all of the HTTP request/response messages is that you must manually map each procedure, class-method, and parameter to a HTTP request/response component using a GUI mapping utility - a very long process if you have more than a few REST APIs. Mike J. From: Piotr Tucholski bounce-piotrtt@community.progress.com Reply-To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Date: Monday, June 1, 2015 at 4:46 AM To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] Mobile project vs REST project ? RE: Mobile project vs REST project ? Reply by Piotr Tucholski I see. So, in which case the REST project will be more useful? Marek Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...