Repository navigation
System Implementation and Architecture
The implementation of my design is almost as was asked of us in the protocol. My web-app has the ability to authenticate itself with the central server on sign in. It also allows the addition of private data and its retrieval from it with the help of a unique password that the user has set up. This process allows for seamless cross-client configurations. In addition, with the use of API-keys, my web-app only allows a user to be online from one web-app at time. This increases security. Additionally, due to the use of fetching private data from the central system, my client web-app allows other users to use it. Fundamentally, my web-app has all the functionality in terms of communication and multi-user usage as was asked of us. On sign in, the user authenticates them-self against the Login server (also known as the central server). Additionally, the user reports themselves as online to the server. If this is successful, they extract their private information from the central server and the web-app is setup appropriately. During logout, the user reports to the Login server that they are now offline. This allows other users to know the client’s current status.
https://github.com/uoa-cs302/2019-Python-ddhy609/wiki/Protocol-Discussion