Design and document sensible URL scheme for gump data
-----------------------------------------------------
Key: GUMP-144
URL: http://issues.apache.org/jira/browse/GUMP-144
Project: Gump
Type: New Feature
Components: Dynagump
Versions: Gump3-alpha-4
Reporter: Leo Simons
We should have permanent URLs for accessing gump data and think of proper url
space management. For example (and just as an example), we might want to have
http://gump.apache.org/results/vmgump.apache.org/public/2005/06/30/12:34/project-summaries/xml-xerces.html
result in the results summary for the xml-xerces project for the "public" gump
run on vmgump.apache.org on 2005-06-30 that started at 12:34am. This URL should
still be the same 3 years from now. We might also want something like
http://gump.apache.org/results/all-runs/last/project-summaries/xml-xerces.html
to get the most recent of those summaries for all runs of all profiles on all
known servers. Or whatever.
URL management requires some up-front planning, so we should do it :-). A nice
example of good permanent URLs is mod_mbox. Ie the url
http://mail-archives.apache.org/mod_mbox/gump-general/200311.mbox/<[EMAIL
PROTECTED]>
is still going to return the same information 5 years from now.
Gump2 is not a good example at all :-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
