Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Now of course this will directly work only within my network. But if I upload this project to Heroku or something similar, would it still work as intended? I'll assume that you actually have the ...
Answer
#1: Initial revision
> Now of course this will directly work only within my network. But if I upload this project to Heroku or something similar, would it still work as intended? I'll assume that you actually have the project working on your network. The only advice I can really give you here is, "Try it and see if it works." And if it doesn't work, debug. > Almost all examples online use WebSocket. I'm unable to understand why because everyone connecting to the my app online will be served by the same controller and append data to the same text file. Or am I completely wrong? The reason most examples use WebSocket is because WebSockets are bi-directional. i.e, the server can push data to the client without being asked for it. Obviously, this is ideal for real-time chat applications, where you want the server to send you chat updates as fast as possible. In your case though, you are using the "repeatedly polling the server for data" method. While theoretically, this would work, it would only update the chat log as fast as the client requests data. Further, depending on how frequently you poll the server, this can be resource intensive on the server because the data is being repeatedly requested even when there are no changes. However, it does have the advantage of not having to maintain an active connection, so if you don't need real-time updates then this is a perfectly viable method.