| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Filefind file limit |
Hello mark! Wednesday October 25 2017 11:10, you wrote to me: Thanks for that and I will increase my system limit if possible. Vince > On 2017 Oct 25 14:36:30, you wrote to Andrew Leary: AL>>> In the future, I can look at possibly splitting large replies AL>>> into multiple messages. VC>> In mbse there is a 60/64k message limit does this still apply in VC>> fido land these days with internet comms used for most if not all VC>> sysops ? > there never was a limit on message size... what everyone has been > seeing is arbitrary limits placed by ""lazy"" coders*... the tech > standard states that message bodies are unbounded which means there is > no limit set... this leaves plenty of room for expansion as technology > grows... we can see this by this very 64k barrier... it used to be > 32k... these days, memory is accessed differently and the barrier is > much much larger... effectively, each system is limited by drive > space*N where N is the number of copies of the message a system makes > when processing the message... copies because of sending to other > systems in a distribution system (eg: fidonet)... > * ""lazy"" coders: those who didn't implement some sort of disk-based > overflow system so they could process messages too large to fit into > the memory allocation scheme of the time... sure, the larger messages > would be processed slower but they would be processed and passed on... > no need for splitting... splitting should be done only when the > messages are stored in a local message base that has arbitrary message > size limits in place... split the message when initially stored... > reassemble it into one when exporting it to other systems (eg: they > rescanned the area)... the ^ASPLIT spec is perfect for this but some > chose to use it at another point in the process... > )\/(ark > Always Mount a Scratch Monkey > Do you manage your own servers? If you are not running an IDS/IPS yer > doin' it wrong... > ... The road to success is often under construction... Vince --- Mageia Linux v5/Mbse v1.0.7.2/GoldED+/LNX 1.1.501-b20150715* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1) SEEN-BY: 15/0 34/999 90/1 116/18 120/331 123/140 128/2 130/20 140/1 218/700 SEEN-BY: 220/60 229/426 230/150 240/1120 250/1 261/38 100 266/404 267/155 SEEN-BY: 280/464 282/1031 1056 292/140 908 320/119 219 340/400 393/68 396/45 SEEN-BY: 633/0 267 280 281 412 640/384 712/620 848 770/1 801/161 189 2320/100 SEEN-BY: 3634/12 5020/1042 @PATH: 250/1 261/38 712/848 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.