> Hi, Stefan. When someone using a satellite connection tries to upload an attachment *or* edit a long entry, it fails and they are presented
> with an "Internal Server Error." This is a huge improvement over the previous behavior of crashing elogd, but we were wondering if there is any
> hope of improving this further so that one can edit large entries or upload attachments over a slow (in this case, satellite) connection. Do
> you have any ideas or plans on working on this further? Apparently ELOG is the "only" service this user has trouble with from home.
There was a timeout of 1 sec. in the elogd daemon, which probably is too short for a satellite connection. Unfortunately I have no satellite here
around to test it, so I "blindly" increased it to 6 seconds in the current SVN version. Please give it a try. You can increase this yourself, its here
in the code at (Rev. 2291) line 28270:
FD_ZERO(&readfds);
FD_SET(_sock, &readfds);
timeout.tv_sec = 6; <----
timeout.tv_usec = 0;
status = select(FD_SETSIZE, (void *) &readfds, NULL, NULL, (void *) &timeout);
so you can change the 6 to 10 or so. The disadvantage of a large value is the following: Suppose you submit an entry, and in the middle of the
submission your browser dies (or the user closes it). If you have a timeout of n seconds, the elogd server will wait that time until it closes the
connection. During this waiting time is cannot respond to other request, so it might look dead. That's why we should not make it too long.
- Stefan |