metallicgloss / discussionnet-chat-platform

Networked client-server communication platform featuring both direct and group messaging.

DiscussionNet Chat Platform

Please note: This script is in a fully working and tested state, however, it should NOT be considered production ready.

This script was initially developed for the module "COMP1549" at the University of Greenwich, demonstrating a client-server communication system through the implementation of a central forwarding server and master client.

Basic project features include

• Graphical User Interface
• Direct Messaging
• Global Group Chat
• User Listing
• Server-Sided Connection Logging
• Master Client Redundancy (Automated Reallocation of Master)

Getting Started

Compatible Operating Systems (As Tested)

• Windows 10 Pro (Version 2004)
• Windows 10 Home (Version 2004)

Looking for more details on the project? Please review Software Documentation - Project Submission.pdf for extra information.

Project Contributors

William P - @MetallicGloss
Adnan T - @AdnanT-ADN
Dan B - @It-is-Dan
Gabriel N - @gabrielnetz

discussionnet-chat-platform's Issues

Controller UI Updates

As the controller, outgoing messages fail to paint correctly on the user interface. Incoming messages appear as normal, but outbound messages don't automatically show - you have to currently hover over, or click, the tab.

Display current coordinator on interface.

Add option to interface to display coordinator in group.

Integration of Group Chat functionality

Integration of group chat functionality with the frontend user interface.

Invalid User ID Selection

Currently, if a user enters a duplicate user ID, the response is sent back as a message; this needs to be sent as an instruction that triggers an action. If this action could be currently configured to simply be a popup message box to tell the user, I (@metallicgloss) can then integrate frontend handling into it to re-direct them back to the auth screen.

User Input Validation

All user fields currently have no forms of validation; validate and sanitise all user inputs through the interface manager.

Types of validation needed:
Required
Min Length
Max Length
Numeric
Within Range (definable)
IP Address Format

Incoming messages appear in wrong channel.

Incoming messages from other users appear in the wrong channel - displayMessage targeting selected component, even for inbound content.

Lingering Debug Code

Could the code to remove the debug print of active connections be dropped from the program please.

Full code clean & commenting run-through.

Upon completion of other outstanding issues, execute a complete code formatting, clean and comment run-through for the project. Standardise commenting format, variable naming convention.

Server Log Syntax Formatting

Adjust formatting or integrate string replacement to allow for the server logs to export to the log table in a nicer readable format.

Network Error Handling

On network error, redirect to startup page - don't close program.

Server Termination - Reconnection Fault

In the event the server terminates unexpectedly, clients are kicked back to the setup page but object still persists (meaning the port cannot be re-bound to in the event the user wishes to reconnect).

@AdnanT-ADN - integrate a way to self destroy client object on server disconnection.
@metallicgloss - integrate a method to destroy chat window so previous messages do not persist when reconnected.