On 31 Jan 2020 at 01:09p, g00r00 pondered and said...
Is this a common thing you see where this number is reached? I think I had it set to 100 originally and I expanded it to 200 for you. I do
want to keep some sort of limit in place and not just let it run wild
and queue 15,000 files or something if they are there.
Not that common, but when a node asks for packets and does not poll for a few days it can get into the thousands quickly.. I think either allow for a
manual setting in the BinkP server 0=unlimited or set a number 1-999 files
per session... and allow fidopoll to read that setting also or perhaps lets just try with no limits.
I tend towards allowing limits to be stated by the sysop. What if bandwidth
is an issue or packets are being sent not directly by internet but over RF
via AX.25 etc. then setting some limits would be a good idea :)
I also think for the BinkP server the lower limits are not needed as incoming polls from nodes can occur concurrently so it does not matter if a node is
tied up and pulling down 1200 packets if nodes 2-10 are free for other
But for the current sequential fidopoll it does matter as the next node won't get it's packets until 1200 packets are sent to the node before it. So more reason to have settings for these things, and also for a fidopoll2 that
mimics the multiple outbound polling of BinkD :)
--- Mystic BBS v1.12 A44 2020/01/31 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)