What we'd be looking to do is basically the following, keeping in mind that currently this is all still in SSRS:
Currently in our system we've designed an UI that allows users to create a report list, meaning that they create a name for a list of reports where they can select one or more reports and defining parameters for each of the reports.
Currently when they choose to run the named report list, it displays all the reports in individual report named tabs in a jQuery modal dialog. Depending on how many reports they selected and what the reports are doing this could be quite a few tabs along with taking quite a long time to run. We've managed to balance how the reports run by making it that a report will only start running once a tab is selected. This way if there are 5 tabs, (ie 5 reports), there are not 5 requests/responses. This could still happen if a user gets, "click happy".
Again this was a feature that was needed and is in its first release.
What I have suggested is redesign of this feature so that when the user sets everything up and they choose run what would really happen is the following:
1. A schedule/subscription would be created with a folder location for the reports to be dropped too, that would be defined upon that run of the reports, making it the folder unique to that run, like something like a run ID.
2. After all the report would be finished rendering to PDF and drop to unique run ID fileshare, there would be something that would zip all the PDF files into one file and transferred to the actual "pickup" directory for the user to download the pack.
I believe what you're saying is that we'd be able to create this schedule to run the reports, but we'd need to create something else to monitor the rest of what we are trying to accomplish? I just didn't know if there would be some way that I could create my own assembly that could hook into AR server's scheduling through interfaces or not.