Mirroring The Giant Java TreeAs the GJT grows in size and number of developers, bandwidth will naturally become an issue. The obvious solution is to mirror the site. However, mirroring the GJT is not as simple has a traditional mirror, since the site is very dynamic, and is built on top of several datasources, including the CVS repository, and SQL database.
Since the project is still not completed, and thus is in flux, we have decided not to establish any mirrors until the design has settled down. Once we are ready to mirror, we have to decide exactly what that means. I believe this list helps itemize the most significant things:
So keep these items in mind as you ponder the idea of mirroring the tree.
All contents are licensed under the General Public License.