Pre-Grant Publication Number: 20070135944
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer-to-Patent forwards the Top 10 most relevant prior art submissions and their annotations to the United States Patent and Trademark Office.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | See URL |
Basic Information
| Type of Prior Art | Print Publication |
| Publication Title * | |
| Author | |
| ISBN | |
| Page Range | |
| Medium | Book excerpt |
| Publication Date * | 2004 |
| URL | http://www.jcorporate.com/expre... |
Notes / To Do
| Notes | See how the excerpt has many of the key elements of 2007-135944 |
Excerpt
Excerpt A Controller object can be thought of as a finite-state machine, transitioning from state to state and performing the appropriate business logic at each state. These states comprise the "Model" of your application - it is here that the application interacts with the database, with the user, with files and other resources, and does it's processing. So if each state represents a particular step or unit of processing, the controller can be thought of as a (finite-state) machine, and the function of transitioning from one state to another is how the controller gets it's work done…...
An Input object is a request from the Controller for the client to supply some information….
An Output object represents a response from the Controller to be presented to the user….
Output's also have "Attributes"….
Blocks
For easier use in JSP's (and other environments) where there are a lot of inputs, outputs and transitions, the concept of "blocks" is available to help keep the controller response organized.
A Block object's purpose is to act as a container for other ControllerElement objects such as Transition, Input, Output and other Block objects. The idea behind a Block object is that it is a logical grouping of other ControllerElement objects for presentation purposes. Think about a HTML page which has multiple sections (not necessarily HTML frames), with each section having its own text messages, buttons/links and forms. by name, which Input, Output and Transition items were to be grouped together. With Block objects, the Controller writer would group each logical set of Input, Output and Transition objects within a Block, with each logical section of the HTML page getting allocated its own Block. The JSP writer in turn, would simple get an Enumeration of all the Blocks from the controller, iterate over each ControllerElement and then create appropriate HTML for each object. Since a Block returns each ControllerElement in the order it was put into the Block, if a JSP writer did not care, the ControllerElements could be placed in the same order that the Controller writer put them in. Of course, the JSP-writer is still free to access each ControllerElement by name as previously and then do a custom HTML presentation.
|
Relevance
Claims
1
An apparatus for providing a summary for at least one process of a system, the apparatus comprising:
a block object for accepting input data descriptive of the at least one process and for grouping as a block at least one variable of the input data with at least one attribute for the variable; and a display client for reading the block and producing output to display the summary for the at least one process.
Relevance
see excerpt
see excerpt
Claim Chart
All
0 days left
