APPLICATION DEVELOPMENT SYSTEM AND METHOD FOR OBJECT MODELS AND DATAGRAPHS IN CLIENT-SIDE AND SERVER-SIDE APPLICATIONS

• US 20140082586A1
• Filed: 08/08/2013
• Published: 03/20/2014
• Est. Priority Date: 08/09/2012
• Status: Abandoned Application

• Current Assignee: FatFractal, Inc.
• Original Assignee: FatFractal, Inc.
• Inventors: Casey, Gerard Michael
• Application Number:
  US13/962,922
• Publication Number:
  US 20140082586A1
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/35 model driven

Abstract

An application development system and method are provided for object models and datagraphs in client-side and server-side applications of a web-based or cloud-based application deployment platform. The system and method are used for representing, persisting, permitting, traversing, querying, manipulating and extending object models and their imputed datagraphs, in applications spanning the client-side and server-side of the web-based or the cloud-based application deployment platform.

Claims

1. An application development platform, comprising:

one or more computing resources that host a backend system;

one or more connected devices that connect to the backend system;

each connected device having a memory that stores a plurality of lines of client side code of an application having a data model;

the backend system having a store that stores a plurality of lines of server side code of the application having the data model; and

the backend system having a backend state representation that instantiates an object model based on the data model, wherein the object model is shared across the client side code and the server side code.

2. The platform of claim 1, wherein the backend system has a GRABBAG backend data-type that is separate from the object model and stored by the backend system.

3. The platform of claim 2, wherein the GRABBAG data-type has a set of object pointers that point to one of one or more objects in a collection and any object from any collection.

4. The platform of claim 2, wherein the backend system automatically generates a back reference for each object in the object model, the back reference for a particular object containing a list of other objects that refer to the particular object.

5. The platform of claim 2, wherein the backend system further comprises an access control list for each object in the object model.

6. The platform of claim 2, wherein the backend system further comprises a query language that allows a user to traverse a datagraph associated with the object model.

7. The platform of claim 1, wherein default permission controls in the form of access control lists are defined as rules for all objects created in a collection.

8. The platform of claim 7, wherein the default permissions can be defined to be inherited from other objects that are referred to by the object model.

9. The platform of claim 1, wherein backend system is one of a cloud based system and a web based system.

10. The platform of claim 1, wherein each connected device is a processing unit based device that has one or more processing units, memory, a display and connectivity.

11. A method for developing an application, comprising:

providing a backend system and one or more connected devices that can connect to the backend system;

providing, in one of the connected devices, a plurality of lines of client side code of an application having a data model;

storing, in a store of the backend system, a plurality of lines of server side code of the application having the data model;

instantiating, in the backend system using a backend state representation, an object model based on the data model; and

sharing, by the backend system, the object model across the client side code and the server side code.

12. The method of claim 11 further comprising providing, by the backend system, a GRABBAG data-type that is separate from the object model and stored by the backend system.

13. The method of claim 12, wherein the GRABBAG data-type has a set of object pointers that point to one of one or more objects in a collection and any object from any collection.

14. The platform of claim 12 further comprising automatically generating, by the backend system, a back reference for each object in the object model, the back reference for a particular object containing a list of other objects that refer to the particular object.

15. The method of claim 12, wherein the backend system further comprises a default access control rule for each object in the object model.

16. The method of claim 12, wherein the backend further maintains an access control list for each object that can be programmatically changed by the client-side code or server-side code.

17. The method of claim 16, wherein the rule that defines the access control list for each object in the object model can be defined to be inherited from other objects that are referred to by the object model.

18. The method of claim 12 further comprising providing, by the backend system, a query language that allows a user to traverse a datagraph associated with the object model.

19. The method of claim 11, wherein backend system is one of a cloud based system and a web based system.