Abstract: A data structure representing the state of courier assignments is described. For each courier assignment, the data structure contains: information identifying a destination location for the courier assignment; information identifying a drop-off protocol specified for the courier assignment, the drop-off protocol specifying a sequence of steps; and, for each of at least some of the steps of the identified drop-off protocol, a representation of compliance evidence collected with respect to the step of the courier assignment. The contents of the data structure are usable to present collected compliance evidence for steps of the drop-off protocol specified for courier assignments among the plurality of courier assignments, either contemporaneously or at later times.

Abstract: A data structure representing the state of courier assignments is described. For each courier assignment, the data structure contains: information identifying a destination location for the courier assignment; information identifying a drop-off protocol specified for the courier assignment, the drop-off protocol specifying a sequence of steps; and, for each of at least some of the steps of the identified drop-off protocol, a representation of compliance evidence collected with respect to the step of the courier assignment. The contents of the data structure are usable to present collected compliance evidence for steps of the drop-off protocol specified for courier assignments among the plurality of courier assignments, either contemporaneously or at later times.

Abstract: A data structure representing the state of courier assignments is described. For each courier assignment, the data structure contains: information identifying a destination location for the courier assignment; information identifying a drop-off protocol specified for the courier assignment, the drop-off protocol specifying a sequence of steps; and, for each of at least some of the steps of the identified drop-off protocol, a representation of compliance evidence collected with respect to the step of the courier assignment. The contents of the data structure are usable to present collected compliance evidence for steps of the drop-off protocol specified for courier assignments among the plurality of courier assignments, either contemporaneously or at later times.

Abstract: A data structure representing the state of courier assignments is described. For each courier assignment, the data structure contains: information identifying a destination location for the courier assignment; information identifying a drop-off protocol specified for the courier assignment, the drop-off protocol specifying a sequence of steps; and, for each of at least some of the steps of the identified drop-off protocol, a representation of compliance evidence collected with respect to the step of the courier assignment. The contents of the data structure are usable to present collected compliance evidence for steps of the drop-off protocol specified for courier assignments among the plurality of courier assignments, either contemporaneously or at later times.

Abstract: A method. A JavaScript (JS) object is instantiated. The instantiated JS object processes application programming interface (API) requests received from mobile devices. The instantiation of the JS object is based on a JS model including (1) a JS file that stores a description of a behavior of the JS object and (2) a JS object notation (JSON) file that stores a description of properties of the JS object. The JSON file includes at least one validation rule to reject a data tuple unless the data tuple meets a required constraint specified in the validation rule. A data abstracter is an interface between the JS object and a set of data storages from which the JS object retrieves data while processing at least two of the API requests. The data abstractor is connected with the set of data storages by implementing a data exchange logic for the set of data storages.

Abstract: A method. A JavaScript (JS) object is instantiated. The instantiated JS object processes application programming interface (API) requests received from mobile devices. The instantiation of the JS object is based on a JS model including (1) a JS file that stores a description of a behavior of the JS object and (2) a JS object notation (JSON) file that stores a description of properties of the JS object. The JSON file includes at least one validation rule to reject a data tuple unless the data tuple meets a required constraint specified in the validation rule. A data abstracter is an interface between the JS object and a set of data storages from which the JS object retrieves data while processing at least two of the API requests. The data abstractor is connected with the set of data storages by implementing a data exchange logic for the set of data storages.

Abstract: Some embodiments of the invention provide a novel server for processing application programming interface (API) requests. In some embodiments, the API server is written in JavaScript. For example, in some embodiments, the API-accessible objects of this server are each defined in terms of a JavaScript file and a JSON (JavaScript Object Notation) file. At runtime, a runtime processor instantiates each JavaScript object from its associated JavaScript and JSON files. Once instantiated, the JavaScript object can be used to process API requests that refer to the JavaScript object. Some embodiments use novel JSON file structures that allow these embodiments to define rich JavaScript models.

Abstract: Some embodiments of the invention provide a novel server for processing application programming interface (API) requests. In some embodiments, the API server is written in JavaScript. For example, in some embodiments, the API-accessible objects of this server are each defined in terms of a JavaScript file and a JSON (JavaScript Object Notation) file. At runtime, a runtime processor instantiates each JavaScript object from its associated JavaScript and JSON files. Once instantiated, the JavaScript object can be used to process API requests that refer to the JavaScript object. Some embodiments use novel JSON file structures that allow these embodiments to define rich JavaScript models.

Abstract: Some embodiments provide a system and method for dynamically determining whether to execute a function locally or remotely for an application operating on a first device. The method, while the application is operating, identifies a set of conditions the evaluation of which dynamically determines whether to (i) direct a second device to remotely process a function or (ii) locally process the function on the first device. The method evaluates the identified set of conditions on the first device. When the evaluation of the set of conditions corresponds to remote processing of the function, the method directs the second device to process the function and return a response to the first device. When the evaluation of the set of conditions corresponds to local processing of the function, the method processes the function on the first device.