# New Functionality for Moodle E-Learning Platform: Files Communication by Chat Window
## 3 Purpose of Sending Files through the Chat Window
### Analyzing the Impact of the Developed Method
The browsers used were Internet Explorer, Microsoft Edge, Mozilla, and Google Chrome, the latest versions, thus aiming to test the compatibility of the solution with these browsers. During this testing, no performance degradations of the systems were identified, and no side effects occurred, such as increased network traffic or performance degradation at the level of the servers hosting the IT solution. The amount of secondary storage and the security of file storage did not undergo adaptations or adjustments; the same solution and logic already provided by the IT platform was employed. The file-sending and storage modes were kept as in the previous solution. Saving them is done locally on the user's station; they are not stored in hardware spaces related to the server. Thus, the technical characteristics related to memory, processor, and storage space are not affected by the implementation of this solution. The server is provided with SSD storage. The backup is performed at the platform component level. The server is configured to  
Figure 1: Comparison of the implemented method before and after sending the files. perform incremental backups every day, an operation that is scheduled to be performed every night through a job that launches a script created for this purpose. On weekends, a full backup is performed every Sunday, an operation that is scheduled to be performed at night, through a job that launches a script created for this purpose. There is a backup configured at the storage level. Incremental backup is performed every day, an operation that is scheduled to be performed every night through a job that launches a script created for this purpose. The server on which the e-learning platform is installed is large enough to cope with over 2500 users and to support at least 1500 simultaneous logins. The way files are transmitted and stored does not affect or bring any degradation to the platform because this operation of transmitting and opening files has a minimal cost in terms of processing on the server. From the point of view of system security analysis, on each workstation from which the platform was accessed, there are installed antivirus programs (BitDefender, Windows Defender) and anti-spyware programs (Spybot, Search&Destroy), as well as a management console (ManageEngine). Security information was collected from Windows logs, system logs, and application-specific logs, as well as other related programs, to see if there were errors, security breaches, vulnerabilities, and cyberattacks. The simulations were run over 30 days, and the logs were checked every 24 h. Logs reported multiple phishing attacks and antivirus programs were able to block these attempts, leaving the platform and workstations unaffected. The value in the Table 3 represents the average of three scans performed during one day. From the actions taken regarding the scans that were done three times a day (at 09.00, 12.00, and 15.00) for 30 days and the results obtained, as shown in Table 3, the following can be observed: Only two spam attacks and no viruses were discovered as a result of the antivirus program's three daily scans. As a result of scans performed by the antivirus program for a week, only nine spam attacks, and no viruses, were found. After thirty days of anti-virus scanning, only seventeen spam messages and no viruses were found. As a result of three LAN/WAN monitoring sessions per day, a total of 8 Kbps/s was sent and 252 kbps/s was received. As a result of weeklong monitoring at the LAN/WAN level, 17 Kbps/s was sent and 296 kbps/s was received. As a result of thirty-day monitoring at the LAN/WAN level, 24 kbps/s was sent and 273 kbps/s was received. Following the monitoring performed three times a day at the Windows system information/manage engine level, 6 warnings were received, 2 incidents were identified, and no problem was reported. Following the monitoring carried out for one week at the Windows system information/ManageEngine level, 14 warnings were received, five incidents were identified, and no problem was reported.