Cytoscape Wiki|
← Revision 3 as of 2008-11-21 13:02:46
Size: 2375
Comment:
|
← Revision 4 as of 2008-11-21 13:35:26 →
Size: 2955
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| ~-''Provide a brief description of the purpose and goals of project.''-~ | ~-''How the production and consumption of events should be handled; in particular how plugins interact with each other, the model(s), view(s), etc.''-~ |
| Line 10: | Line 10: |
| ~-''Describe why this project is being proposed and what issues are addressed.''-~ | ~-''Concerns have been raised on several fronts regarding event handling that cannot be addressed by simple (existing) Java patterns, largely because the application is not monolithic but is made up of independently moving parts.''-~ |
| Line 13: | Line 13: |
| ~-''Provide examples of how the products of this project will be used.''-~ |
This is less a listing of use cases as it is issues and concerns; an outline of what any solution should attempt to address: 1. '''Batching''': The case where many events (like the creation of many nodes) could possibly be grouped together as opposed to handling each one discretely. 2. '''Transactions''': Plugins should leave the model in a valid state, and conflicting changes by different plugins prevented. |
RFC Name : Event Handling |
Editor(s): BrianTurner |
Date: Nov 21 2008 |
Status: Draft |
Proposal
How the production and consumption of events should be handled; in particular how plugins interact with each other, the model(s), view(s), etc.
Background
Concerns have been raised on several fronts regarding event handling that cannot be addressed by simple (existing) Java patterns, largely because the application is not monolithic but is made up of independently moving parts.
Use Cases
This is less a listing of use cases as it is issues and concerns; an outline of what any solution should attempt to address:
Batching: The case where many events (like the creation of many nodes) could possibly be grouped together as opposed to handling each one discretely.
Transactions: Plugins should leave the model in a valid state, and conflicting changes by different plugins prevented.
Implementation Plan
Outline and describe the process and major issues related to implementing this proposal. Illustrate your plan when possible. Try this free online tool for making diagrams -> [http://www.best4c.com/editor/NetMapApplication.jsp Best4c] (draw; save; then insert hyperlink into this page)
Project Management
Project Timeline
Provide a timeline for implementation. Insert a graphic if you can. Try this free online tool for making project timelines -> [http://www.helpuplan.com/index.asp Help-u-Plan] (create a new chart; modify; right-click to save gif; then attach to this page)
Tasks and Milestones
Outline the major milestones and tasks involved in implementation.
Milestone 1: …
- Task 1: ...
- Task 2: ...
Milestone 2: …
Project Dependencies
Outline and projects that depend on this project, link to relevant RFC's and note at what point dependent projects could be started.
Related RFCs
Link to other related RFCs
Issues
List any issues, conflict, or dependencies raised by this proposal
Comments
Add comment here…
How to Comment
Edit the page and add your comments under the provided header. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.