A
agent_008_nl
Guest
Thanks Bronco. I do not get what you mean with your issue on the JSDO. Can you give an example of a problem in a bit more detail, understandable for a webdummy like me? Can anyone else deeper into JSDO / REST etc. elaborate on the pros and cons of using the JSDO? On the pros I read: From www.progress.com/.../Track%201%20-%20Progress%20OpenEdge%20Mobile%20and%20Bits%20Involved.pdf: REST Hurdles: It is possible to access data on a server prior to OpenEdge 11.2 •For example using JavaScript XMLHttpRequest( ) •Very labor intensive to write and maintain low level code Functionality offered by JSDO: Support for tracking changes Transparent access to OpenEdge REST web services Implementation details are hidden Developers do not need to know the URIs Local Storage and Offline transport support Change tracking Using generic REST Service for development in Mobile App builder will leave out JSDO features. From oemobiledemo.progress.com/.../index.html “instead of a Mobile App having to identify the URI, send an HTTP request, and interpret the HTTP response for a given REST resource (AppServer routine call), it only has to call the appropriate JavaScript method or methods on the JSDO to execute the corresponding ABL routine in the class or procedure object on the AppServer. All input parameters, output parameters, and other results of ABL routines are exchanged with the JSDO and its JavaScript methods as corresponding properties of JavaScript objects that the Mobile App passes and returns from the JSDO and its methods.” “a Mobile service supports some or all of the following Mobile operations that access data and business logic on the AppServer over the network: • Create — A single operation that creates a single new record on the AppServer. • Read — A single operation that reads a set of records from the AppServer. • Update — A single operation that modifies a single existing record on the AppServer. • Delete — A single operation that deletes a single existing record on the AppServer. • Submit — A single operation that can perform one or more create, update, and delete operations in a single transaction on the AppServer. A Mobile resource supports this operation only if you define it to access a ProDataSet with temp-tables that use before-imaging." -- Kind regards, Stefan Houtzager Houtzager ICT consultancy & development www.linkedin.com/in/stefanhoutzager
Continue reading...
Continue reading...