 |
 |
> A transfer protocol should have the option to limit the number of connections to the server that it serves the data from. I think limiting the file system assumes the file system isn't supporting other applications. This isn't limiting the filesystem but rather the filesystem plugin for XRootD. Why is it obvious there's a different set of limits when doing this via the XRootD protocol versus HTTP and that these should be handled independently? That is, let's say the server can support 100 concurrent file transfers at a time. What's the value we should have for the xrootd and HTTP? I would claim it's better to just say "transfer up to 100 files at a time, regardless of how they came in the door". -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1601#issuecomment-1029367408 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1