Accomplishments this week
1. Robust Web Application Construction
- Since our last demo meeting, we get advice from the professor and TA that we should consider the user experience of our customers and make the web application able to handle possible edge cases so that it does not crash.
- Firstly, I added the end session logic between the web application and the tracker program. Now when the user presses the end session button on display.html, the RPI session being used by the user is released and will be able to be released to other users. This is achieved by a threading program in python, which waits for an asynchronous interruption from the web application when the user presses the end session button. As soon as the asynchronous interruption is received by the tracker program, the tracker program aborts the thread which is executing the current tracker program associated with the current user. Then, the user will be redirected to the connect page again. Meanwhile, the tracker program gets reset and waits for the next user.
- Secondly, I added the OnetoOne relationship between the RPI and the user. Now, when the user logs in, two possible scenarios occur: (1). The user has not been connected with an RPI instance yet and will be directed to the connect RPI page (2). The user has already been connected to an RPI instance, yet have not yet ended his/her session before logout/closes the website, then he/she will be directed to the select-page page, which means that they will not be able to connect to an RPI (one user can only connect with on RPI).
- The pages mentioned above are shown below, which represents the basic workflow of the website.
Progress for schedule:
- On schedule
Deliverables I hope to accomplish next week:
- successfully run the integration on AWS
- more web app handling
0 Comments