Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
|
|||
|
|||
|
Notes:
|
Brainstorming on page flow for physically uploading a file from adilas to the adilas content server: (Please see sketches & flow on scan in photo gallery) Normal Flow: Cluster Model: - Different clients connected to a data server - Normal high speed data path or highway - Different data servers - Bigger more robust content server - Outbound messenger called a web service going from the content server back to the data server - Files will be stored here on the content server - In bound file submission or uploading a physical file to the content server Flow with Content & Web services: - Clients & users Page flow for all three buttons: - Step 1 in adilas (with this option): - Step 2 in adilas o Form o ID o File o Name o Desc - Step 3 in adilas o Action page o Insert into database - Step 4 in adilas o View results - Step 2 in adilas o Message & button - Step 3 on content server o Form o ID o File o Name o Desc - Step 4 on content server o Upload the file - Step 5 send the runner o Web service and show completion - Stop: o Dead end – close when done For both local and remote file reference, everything stays in adilas and goes full circle. On the physical upload, open a new browser window and go until complete. The web services will tell the data server once complete. |