| | 58 | |
| | 59 | The launch sequence for a Fusion application will be as follows: |
| | 60 | |
| | 61 | A new fusionviewer.php script will be added (with jsp and asp versions TBD), which will take one GET parameter, appdefn=Library://... This script will: |
| | 62 | |
| | 63 | - authenticate (using anonymous by default) |
| | 64 | - create session |
| | 65 | - retrieve appdefinition |
| | 66 | - parse template location |
| | 67 | - redirect to template, passing session and app definition path |
| | 68 | |
| | 69 | The javascript in the default templates will parse out the session and app definition and initialize Fusion with those parameters. |
| | 70 | |
| | 71 | The javascript in the default templates will also provide the option of hard-coding the app definition (for copying and deploying). |
| | 72 | |
| | 73 | The javascript in the default templates will be reponsible for creating a session with the server if one is not passed in, then initializing Fusion with the session and app definition. |
