Hey Jules, hey all, we're reading data from our server via <URL::createInputStream>:
const int connectionTimeOutS = 30; const ScopedPointer<InputStream> in(m_url.createInputStream(usePostRequest, openStreamProgressCallback, nullptr, String::empty, connectionTimeOutS * 1000));
The server needs 90 seconds to process the request, but sends some text saying "Wait\n" every 5 seconds. For most users this works flawlessly, <InputStream> is created almost immediately. We're then periodically calling <in->readNextLine()>, get a "WAIT\n" line every 5 seconds and the data after 90 seconds. No problem with timeout at all.
But: For some users, we are stuck in the line of creating <InputStream> until the timeout is hit after 30 seconds.
It we then change <connectionTimeOutS> to 1000 seconds, the creation of <InputStream> needs 90 seconds, until the whole data is received from the server at once. The bad thing is, that we cannot savely close our program during these 90 seconds.
It happens on both Windows and Mac. So I am wondering if anyone stumbled across this and has an idea about this issue?