Since Wei left comments about 1 and 5, here's some thoughts on the others:
- 2: Not obvious how to bootstrap autorm-type concepts onto the HTTP protocol If there is some part of HTTP that has similar ideas, we can certainly look at implementing it... but would be slightly reluctant to invent something new.
- 3: Just checked the code. Number of streams has a sanity limit (can't go over 100 / transfer) but otherwise is based on the client request.
- 4: This was recently added to the throttling plugin. I think the filesystem level is an appropriate place to put limits given that the storage resources are shared between HTTP and XRootD.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1601/1024999688@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1601#issuecomment-1024999688",
"url": "https://github.com/xrootd/xrootd/issues/1601#issuecomment-1024999688",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
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