Write a Python Event and Trigger Client Application
Budget: $30 – $250 USD
The “application” should be supplemented with supporting libraries for Windows 8 and newer, Mac OS and Linux. The default interfacing language of the application should be the user’s Operating System’s language. If the interfacing language is not available because it has not been implemented, the default language must be English. Moreso, the application’s GUI language design should be stored in separate files for each modification (one file per language). Each supported language should be in a key-value dictionary stored in separate file.
The “application” should be able to successfully connect to a main authentication server over a HTTPS connection and POST a username and password. After successful authorization, the server will issue a JSON message with a token for the application, which will contain as a session key and a flag for successful/unsuccessful authorization. If authorization fails, the user should be presented with a relevant message in their selected language.
Next, the application should connect to an asynchronous Web Socket and submit the session key in JSON format and wait be greeted by the Web Socket server (or be rejected). Should at anytime the server issue a disconnect message, the application should terminate the Web Socket, alert the user and return to the sign on screen.
After being successfully greeted, the “application” should listen for incoming events and trigger the correct model based on the type of event. These events are outlined below.
The “application” should reside in the system tray of the Operating System (near the system clock). When double clicked, depending on the state of the application, the User should have the option to login or to disconnect or exit.
SEE ATTACHMENT FOR FULL SCOPE
The “application” should be able to successfully connect to a main authentication server over a HTTPS connection and POST a username and password. After successful authorization, the server will issue a JSON message with a token for the application, which will contain as a session key and a flag for successful/unsuccessful authorization. If authorization fails, the user should be presented with a relevant message in their selected language.
Next, the application should connect to an asynchronous Web Socket and submit the session key in JSON format and wait be greeted by the Web Socket server (or be rejected). Should at anytime the server issue a disconnect message, the application should terminate the Web Socket, alert the user and return to the sign on screen.
After being successfully greeted, the “application” should listen for incoming events and trigger the correct model based on the type of event. These events are outlined below.
The “application” should reside in the system tray of the Operating System (near the system clock). When double clicked, depending on the state of the application, the User should have the option to login or to disconnect or exit.
SEE ATTACHMENT FOR FULL SCOPE