feedreader-development

[Feedreader-development] server response timeout value

[Toomas T. <to...@i-...>]

Hello!

Is there any special meaning for this row:

  Feedretrieval_Timeout = 15000;  // Time in msec, that TIdHTTP waits 
for a server response

I think that 15seconds is quite small time. For example a lot of feeds 
that are abroad give me timeout with this value. It's better if this 
timeout is for example 120 seconds. With that we make sure that all 
normal (but not always responsive) feeds get downloaded.

What do you think?

And another problem is our Feedreader lockdown problem :) You know, then 
user can't close feedreader/cannot see toolbar. I still sometimes get 
this. Problem is that if I "end task" then all feed updates are gone and 
all my read messages are unread. I will try to make feedreader save 
feeds and headlines for example once in hour...?

Greetings
Toomas

Re: [Feedreader-development] server response timeout value

[Nicole S. <ni...@gn...>]

Toomas Toots <to...@i-...> wrote:
>timeout is for example 120 seconds. With that we make sure that all 
>normal (but not always responsive) feeds get downloaded.

Btw Sharpreader has this nice feature of not showing an error popup but
write a feedentry with it's error message. How about a user setable time?

>all my read messages are unread. I will try to make feedreader save 
>feeds and headlines for example once in hour...?

No, not enough. As said before, this is nice for an automation saving
feature but I do get my feeds downloaded in about 5-10 minutes and am
screwed in the middel of it. 

Nicole
	
-- 
http://www.useful-sounds.de/ - http://beissholz.de

Re: [Feedreader-development] server response timeout value

[Karsten H. <kh...@kh...>]

Toomas Toots wrote:

> Hello!
> 
> Is there any special meaning for this row:
> 
>  Feedretrieval_Timeout = 15000;  // Time in msec, that TIdHTTP waits for 
> a server response
> 
> I think that 15seconds is quite small time. For example a lot of feeds 
> that are abroad give me timeout with this value. It's better if this 
> timeout is for example 120 seconds. With that we make sure that all 
> normal (but not always responsive) feeds get downloaded.
> 
> What do you think?

Ok, done.

> 
> And another problem is our Feedreader lockdown problem :) You know, then 
> user can't close feedreader/cannot see toolbar. I still sometimes get 

Screenshot? Whats the content of the file "debug.txt" in the exe directory after 
such a crash?


Karsten