OpenEdge Development: Mobile Applications - Product ...

progress.data.JSDO class
When you instantiate a JSDO, it relies on a prior login session that you can establish
using an instance of the progress.data.Session class. This login session enables
optionally secure communications between the client JSDO and the Web server,
specified Mobile services, and ultimately the AppServer that implements the Mobile
resource accessed by the JSDO.
Constructors Two constructors are available for the JSDO. The first constructor takes the name of
the corresponding Mobile resource as a parameter; the second constructor takes an
initialization object as a parameter:
Syntax
progress.data.JSDO ( resource-name )
progress.data.JSDO ( init-object )
resource-name
A string expression set to the name of a resource provided by a Mobile service for
which a login session has been started.
init-object
An object that can contain any writable JSDO properties. It must contain the
required JSDO name property, which specifies the Mobile resource for the JSDO.
It can also contain either or both of the following initialization properties:
• autoFill — A Boolean that specifies whether the the JSDO invokes its
fill( ) method upon instantiation to initialize its local storage with data from
the Mobile resource. The default value is false.
• events — An object that specifies one or more JSDO event subscriptions,
each with its properties represented as an array, with the following syntax:
Syntax
events : {
'event' : [ {
[ scope : object-ref , ]
fn : function-ref
} ] [ ,
'event' : [ {
[ scope : object-ref , ]
fn : function-ref
} ] ] ...
}
event
The name of an event to which the JSDO instance subscribes. See
Table 13 for a list of available JSDO events.
156 OpenEdge ® Development: Mobile Applications