[p4] p4 uri

Jeff A. Bowles jab at pobox.com
Sat Aug 4 19:37:53 PDT 2007

Richard Brooksby, in his Perforce 1999 User Conference paper,
talked about having depots named
This made his Perforce pathnames look like:
And he could easily prepend "http:" to it and feed it to
a web  browser. The P4DB / P4Web app on that machine would
take it from there.

There are lots of ways to do this, but Richard's is a terrific model to imitate.

   -Jeff Bowles
   Perforce Consulting Partner

On 8/4/07, Roger Day <roger.day at globalgraphics.com> wrote:
> I currently maintain 2 SCM systems - an internal one and P4. To allow my
> scripts to process references to files in both SCM systems with standard
> URL classes (in python) I'm thinking of using a URL-like string to
> identify files in either system .i.e
> hope://<hostname>/<filepath>
> p4://<hostname>/<filepath>
> with depot dropping out as the default. Which kinda seems wrong to me. It
> seems to me that the full path should be invoked. But  a full WWW-like URI
> would look like:
> ///depot/
> with hostname and protocol left out for defaults. Any background on why
> the two notations differ?
> What do others do? Is there a recognised or defacto way of addressing p4
> resources similarly?
> Roger
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

Jeff Bowles - jeff.a.bowles at gmail.com

More information about the perforce-user mailing list