[23531] users/jberry/mpwa/doc/design.txt

[source_changes at macosforge.org]

Revision: 23531
          http://trac.macosforge.org/projects/macports/changeset/23531
Author:   jberry at macports.org
Date:     2007-04-03 17:22:42 -0700 (Tue, 03 Apr 2007)

Log Message:
-----------
more thoughts on urls

Modified Paths:
--------------
    users/jberry/mpwa/doc/design.txt

Modified: users/jberry/mpwa/doc/design.txt
===================================================================
--- users/jberry/mpwa/doc/design.txt	2007-04-04 00:12:26 UTC (rev 23530)
+++ users/jberry/mpwa/doc/design.txt	2007-04-04 00:22:42 UTC (rev 23531)
@@ -80,7 +80,9 @@
 
 	- Call it a submissionid or a portid? (perhaps it doesn't matter, as it's really
 	  just an internal number that becomes part of the public porturl, which is what
-	  people really use).
+	  people really use). I'm beginning to think that portid is good, as a submission
+	  of a port can be thought of as a port, and it's shorter, and doesn't suffer from
+	  bringing too much of the action into the name.
 	
 	- It is not determined yet to what degree port meta information should be stored
 	  in the database vs in the submission directory. It's likely that much such
@@ -131,6 +133,9 @@
 	A simple flat/short url to access and/or uniquely identify a port submission
 			(returns the portpackage for the submission)
 		http://port.macports.org/<submissionid>
+		http://portid.macports.org/<submissionid>
+		http://submission.macports.org/<submissionid>
+		http://port.macports.org/id/<submissionid>
 		
 	URLs to port page for a port:
 			(note that the <portname>.macports.org style might preclude use of hostnames
@@ -149,10 +154,27 @@
 		http://port.macports.org/<portname>
 		http://port.macports.org/stable/<portname>
 		
+	Other urls:
+	
+		http://port.macports.org/latest/<portname>
+		
+	Favorites:
+			// Access to port packages
+		http://port.macports.org/id/<submissionid>
+		http://port.macports.org/stable/<portname> (301 redirect to submission)
+		http://port.macports.org/latest/<portname> (301 redirect to submission)
+		
+			// GUI access to port pages
+		http://www.macports.org/category/<category>
+		http://www.macports.org/port/<portname>
+		http://www.macports.org/id/<submissionid>
+		
 Issues for urls:
 
-	- do we have portnames starting with numbers or entirely composed of numbers?
-	- If a port is installed using a url that does a permanent redirect to another port,
+	- do we have any portnames starting with numbers or composed entirely of numbers?
+		yes: port echo 'name:^\d'
+		note port 54321, who's name is composed entirely of numbers.
+	- If a port is installed using a url that does a 301 (permanent) redirect to another port,
 	  the url remembered as the installed port should be the redirected target, rather than
 	  the original. This would allow the url for a stable version of a port to redirect to the
 	  particular submission that is desired, and yet maintain a one-to-one mapping between

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070403/190ca71a/attachment.html