Stewart Honsberger wrote in a message to Sander Nijhof:
 > [tag 32 files limit]
 > I'm just saying (again) that 32 files is not al that many. Imagine
 > maximus allowing only 32 user records.. .
 SH> How often would you want people D/Ling 32 files at one time?
As often as they'd want to.
 SH> Also, how hard is it to downloaad 32 files, then tag and 
 SH> download 32 more? 
Typically when a user here starts a long download you can tell that they've 
walked away for a while because when it's done there's a delay before they 
realize it.
 SH> Besides, it's kind of a PITA to maintain a tagged file list 
 SH> that long, how do you even remember which files are which, and 
 SH> make sure you haven't tagged any by mistake if you have 90 
 SH> files tagged?
You get the list displayed when you finally tell it to download,  that's how. 
Or you use the "edit the list" facilities.  It ain't that big of a deal,  and 
I for one would like to see that particular limit pushed seriously upwards.
I picked max in the first place because there seemed to be a philosophy of 
design in it that suggested that there weren't arbitrary low limits in there 
like there were with other packages that were out at the time,  and I wanted 
to be able to put a *lot* of message bases,  file areas,  or "stuff" in 
either of them if I felt like it.  So far I haven't been disappointed.
Heck,  what are all those files for if not to be downloaded?  I let users do 
what they want with their time on line.  Some come for messages,  some for 
files,  and some for both.  I just had a freq not long ago that pulled 34 
files,  and I don't have a problem with that.  Looking at the download 
counters on my files sections,  whole big chunks of it haven't been even 
touched yet...
What else are they there for?
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------