Relevant ports(26000 is the eve client, but does the launcher download on this port also? Is it plain HTTP port 80 or HTTPS port 443?)
Staying with the network level, or router based solution the user would have benefitted from some guidance on:. In neither case will updating the router firmware alter the behaviour of the TCP transfer between client and server unless there is a bug in the router firmware, which would mean programs other than eve launcher will cause connectivity issues. The network level ( which is the router ) or at the application level ( in this case, the launcher ) with a configuration setting. There are two levels in a network connection best able to address this. Saturation results in the chunks having a longer wait time for the cycle of sending, acknowledgment, and further sending of chunks, like cars stuck in peak hour traffic.
On a saturated link, one program ( the launcher ) already using %100 of the bandwidth will have many more chunks acknowledged than a program that starts up after the link is saturated.
To observers, this looks like a constant flow. If the programs in question use TCP for their connection, they are engaged in a process where the server sends a chunk of information, waits for the client to acknowledge the chunk has arrived, before sending subsequent chunks. The traffic from other programs may be able to reach their server but the response now has to be queued. This symptom is very common with the prevalence streaming media services, where one program consumes %100 of Internet->Router bandwidth. The symptom described by the user was an impact to other program connectivity. This thread could have been moved to the feature request section right then and there. The user asked for an option to limit download speed. Someone with a information technology and technical services background I cringed at this unhelpful response.
0 kommentar(er)
