>> It was, indeed. But, unfortunately, it has been now unresponsive (or >> very slow: downloads need 5 minutes or so to be served) for a couple of >> hours, again!
I tried it for two downloads at different times this weekend and found it was the same. It was also pretty darn slow back during release week, too. I can't think of why it should be slow, since it should just be serving a redirect. Did something change on the backend that we should hear about? Maybe the process should be posted somewhere so that suggestions for improving performance and scalability can be made. -Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
