Modeling User Input and Interaction in Workflow Based Applications
US-2015206079-A1 · Jul 23, 2015 · US
US9916136B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9916136-B2 |
| Application number | US-201615167623-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 27, 2016 |
| Priority date | Dec 29, 2008 |
| Publication date | Mar 13, 2018 |
| Grant date | Mar 13, 2018 |
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.
Interfaces for a continuation-based runtime. Some embodiments described herein are directed to a framework using continuation based runtime interface that pertain to an infrastructure for enabling the creation of a wide variety of continuation-based programs that perform a wide-array of tasks. The infrastructure provides a foundation for building continuation-based, declarative applications of various scale and complexity.
Opening claim text (preview).
What is claimed is: 1. A method of executing continuation-based declarative applications, the method comprising: calling a first interface that represents continuation-based functional behavior, wherein instances of the first interface include imperative code in their bodies that is executed by a processor to perform functions, and wherein the first interface is polymorphic; calling a second interface used to store data in the continuation-based runtime, the interface including a type and a name; calling a plurality of argument interfaces, wherein each of the argument interfaces is a binding terminal that represents the flow of data for instances of the first interface, the plurality of argument interfaces comprising: an inargument interface that has a direction of In; an outargument interface that has a direction of Out; and an inoutargument interface that has a direction of InOut; and calling a second plurality of interfaces, wherein the second plurality of interfaces are used to host instances of continuation-based, declarative programs. 2. The method of claim 1 further comprising, calling a plurality of the interfaces including: an interface used for declaratively composing behavior dynamically using an Activity document object model; an interface used for writing imperative behavior through an Execute method that has access to data resolution and extensions; an interface used for writing imperative behavior through an Execute method that has unfettered access to the full breath of the runtime; an interface used for implementing a continuation-based functional behavior that has a well-known, elevated return value; an interface used for allowing for environment access; an interface that adds async operation support to the interface used for allowing environment access; an interface that adds support for child management, setting up no-persist zones, isolation blocks, and bookmarks; an interface used for the storage of data in a continuation-based program; an interface used for implementing a binding terminal that represents the flow of data for an activity; and an interface used for implementing a snippet of workflow with a specific signature. 3. The computer readable medium of claim 1 , wherein the second plurality of interfaces comprises: an interface used to create a new workflow instance or to load an existing instance; an interface used to provide the interface used to create a new workflow instance or to load an existing instance to host functionality including synchronization, persistence, tracking, and extensions; an interface used for implementing a locus of control for workflow instance management; an interface used for directly running an activity as if it were a method call; and an interface used for implementing a primary entry point for accessing a plurality of hosting services. 4. The method of claim 1 , further comprising calling a third plurality of interfaces, wherein the third plurality of interfaces are used to implement a base layer of activities that add functionality to the continuation-based runtime and that are used to add concrete behaviors that build on top of a core activity model.
Related publications grouped by family.
Answers are generated from the same data shown on this page.