System for exception notification and analysis
US-9213622-B1 · Dec 15, 2015 · US
US10698663B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-10698663-B1 |
| Application number | US-201816237491-A |
| Country | US |
| Kind code | B1 |
| Filing date | Dec 31, 2018 |
| Priority date | Jun 2, 2011 |
| Publication date | Jun 30, 2020 |
| Grant date | Jun 30, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: capturing a meta-data definition of an application by an application object model definition module, wherein the meta-data definition describes the application for at least a plurality of node types; responsive to capturing the meta-data definition of the application, generating, from the meta-data definition of the application, code for the application per node type for the plurality of node types in a code generator module; and generating packaging necessary to deploy the application to the plurality of node types; wherein capturing the meta-data definition of the application comprises capturing a definition of peer-to-peer messaging between the plurality of node types, and wherein generating the code for the application per node type for the plurality of node types comprises generating the code for the application per node type for the plurality of node types that enables the application to communicate peer-to-peer between the plurality of node types in accordance with the captured definition of peer-to-peer messaging between the plurality of node types. 2. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing one or more of language types, VM language types, operating system types, platform types, network types and database types. 3. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing a messaging type between a plurality of node types. 4. The method of claim 1 further comprising compiling the code for the application per node type for the plurality of node types. 5. The method of claim 1 further comprising capturing a definition of peer-to-group messaging including network type and protocol preference. 6. The method of claim 1 wherein capturing the meta-data definition of the application comprises describing an Application Object Model and describing the Application Object Model through an Object Model Repository. 7. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing an object model of the application and capturing meta-data for the object model of the application. 8. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing whether the application is persistable. 9. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing whether the application is location-aware. 10. The method of claim 1 wherein capturing the meta-data definition of the application comprises capturing whether the application is mobile. 11. A system comprising at least one processor and an operatively associated memory, wherein the at least one processor executes a plurality of modules comprising: an application object model definition module that captures a meta-data definition of an application, wherein the meta-data definition describes the application for at least a plurality of node types; a code generator module that, responsive to the capture of the meta-data definition of the application, generates application code for the object model of the application defined through the application object model definition module and generates a package necessary to deploy the application to the plurality of node types; and an application node connectivity module that allows the user device to define the plurality of node types to participate in the application, wherein the code generator module generates the application code for the object model of the application for each of the plurality of node types; wherein the application node connectivity module allows the user device to define peer-to-peer messaging between the plurality of node types, and wherein the code generator module generates the application code that enables the application to communicate peer-to-peer between the plurality of node types in accordance with the defined peer-to-peer messaging between the plurality of node types. 12. The system of claim 11 wherein the application node connectivity module allows the user device to define peer-to-peer messaging between the plurality of node types including network type and protocol preference. 13. The system of claim 11 wherein the code generator module generates the application code that enables the application to communicate peer-to-peer between the plurality of node types in accordance with the defined peer-to-peer messaging between the plurality of node types including network type and protocol preference. 14. The system of claim 11 further comprising one or more class libraries or executable libraries per node type, wherein the code generator module generates the application code for a node type with reference to the respective one or more class libraries or executable libraries. 15. The system of claim 11 wherein the application object model definition module captures the meta-data definition of the application comprising one or more of language types, VM language types, operating system types, platform types, network types and database types. 16. The system of claim 15 wherein the meta-data definition comprises at least one indicator that indicates whether the application is persistable. 17. The system of claim 15 wherein the meta-data definition comprises at least one indicator that indicates whether the application is location-aware. 18. The system of claim 15 wherein the meta-data definition comprises at least one indicator that indicates whether the application is mobile. 19. A non-transitory computer-readable medium storing computer-executable instructions for execution by at least one processor, that, when executed by the at least one processor, cause the at least one processor to: provide an interface by an application object model definition module that allows a user device to enter a meta-data definition of an application, wherein the meta-data definition describes the application for at least a plurality of node types, and wherein the meta-data definition comprises a definition of peer-to-peer messaging between the plurality of node types; responsive to the user entering the meta-data definition of the application, generate, from the meta-data definition of the application, application code for the application per node type for the plurality of node types in accordance with the definition of peer-to-peer messaging between the plurality of node types; and generate packaging necessary to deploy the application to the plurality of node types; wherein generating the application code for the application per node type for the plurality of node types comprises generating the application code for the application per node type for the plurality of node types that enables the application to communicate peer-to-peer between the plurality of node types in accordance with the definition of peer-to-peer messaging between the plurality of node types. 20. The non-transitory computer-readable medium of claim 19 wherein the at least one processor is caused to compile the application code for the application per node type for the plurality of node types.
Related publications grouped by family.
Answers are generated from the same data shown on this page.