Issue & Task #1. Ping messages

[MikhailNikolaenko]

Link to issue: EpicGamesExt#34 (comment)

Issue Summary:
Disconnection events are not being triggered in the Frontend Library when unexpected network interruptions occur (e.g., Wi-Fi is turned off). This issue extends to the Signalling Server, which fails to handle such disconnections, leaving it unavailable for new users. This problem presents a significant reliability concern and could be perceived as a bug due to the lack of recovery from disconnection events.

Risk Assessment:

Technical Complexity and Implementation Risk: The implementation of a heartbeat mechanism involves both the frontend library and the signalling server. This introduces complexity due to potential integration issues. Mitigation: Conduct thorough testing in a controlled environment before deployment. Use modular programming techniques to isolate changes and facilitate debugging.
Risk of Unforeseen Side Effects: Changes to the communication protocol might introduce latency or other performance issues. Mitigation: Benchmark performance both before and after implementing the new feature to ensure that the heartbeat mechanism does not degrade system performance.
Compatibility with Existing Infrastructure: There's a risk that the new heartbeat mechanism may not be fully compatible with all existing setups, especially older or non-standard configurations. Mitigation: Provide detailed documentation and versioning guidelines, and consider backward compatibility during design.
Resource Availability: Implementing a robust solution might require more resources than anticipated, affecting other project timelines. Mitigation: Properly scope the work upfront, and allocate additional resources or adjust timelines as necessary based on early progress and findings.

Process Plan:

Software Development Process:
Agile Methodology: Use agile practices to manage the development of this feature.
Quality Assurance:
Automated Testing: Develop and maintain a suite of automated tests, including unit tests for individual components and integration tests for the entire heartbeat feature.
Manual Testing: Conduct manual testing scenarios that mimic real-world disconnections to ensure the system behaves as expected under a variety of conditions.
Communication and Collaboration:
Documentation: Keep thorough documentation of the development process, decisions made, and changes implemented, ensuring that all contributors are aligned.
Integration Strategy:
Continuous Integration (CI): Use CI tools to automatically build and test the application whenever changes are made, ensuring early detection of integration issues.