Jeff Garland writes:
Aleksey Gurtovoy wrote:
Same for a developer, actually, who usually wants to track only a couple of libraries. The problem with such scheme is that it by definition bumps up requirements on the reports' hosting site. Right now the pages are nothing but plain HTML. Ideally, to handle the kind of dynamic requests you describe in real time we need a database backend, and that severely limits where the reports can be hosted. If we as a group decide that the benefits of having something like this outweigh the downside, this can be pulled off quite easily.
BTW, I was only suggesting this for the release results not the daily builds.
Oh, OK.
For the release the idea would be to post-process the xml data into a pre-processed data set that could be coupled with a simple form written in something like php to take the query and display results. That way we wouldn't be bumping up the hosting requirements, but would be improving the user experience. I'm certain this wouldn't be too hard to do...
With certain limit on granularity of "filtering", sure. -- Aleksey Gurtovoy MetaCommunications Engineering