4 messages in com.perforce.perforce-userExtending Webkeeper| From | Sent On | Attachments |
|---|---|---|
| Raym...@orion.no | 14 Apr 1999 07:24 | |
| Greg...@acm.org | 14 Apr 1999 10:50 | |
| Chas...@luna.com | 14 Apr 1999 12:54 | |
| Chri...@wrq.com | 14 Apr 1999 15:15 |
| Subject: | Extending Webkeeper |
|---|---|
| From: | Greg...@acm.org (Greg...@acm.org) |
| Date: | 04/14/1999 10:50:47 AM |
| List: | com.perforce.perforce-user |
For versions of Perforce greater than 98.2 (I think), there is an undocumented "p4 dirs" command. It has some weirdnesses, but it was something I requested a long time ago that they finally added.
It works great if you just want to list the directories in a directory. The weirdness was with the "..." wildcards, I think, and is probably why it is not documented. They may have fixed that by now.
I used it for p4dir, and it sped things up tremendously. You use it just like p4 files.
-Greg.
------ Original Message ----- From: Raymond Wiker <raymond at orion.no> To: <perforce-user at perforce.com> Sent: Wednesday, April 14, 1999 7:25 AM Subject: Extending Webkeeper
I'm working on extending WebKeeper so that it can be used to browse projects, instead of serving up single files.
At the moment I'm looking at strategies for finding all files and directories in a given (depot) directory. The files are trivial; I can simply use "p4 files file://depot/path/to/my/directory/*" to list all files. Directories are more tricky; if I had a guarantee that there would be at least one file in each depot directory, I could use "p4 files file://depot/path/to/my/directory/*/*", snip away the filenames and remove duplicate directories.
In our system, there *are* directories that do not contain any files, and so this strategy fails. I *could* use "p4 files file://depot/path/to/my/directory/...", but this takes a *long* time to execute.
Is there any way to achieve what I want from within the Perforce API? I know that recent versions of P4Win are much faster to start up than before, and I suspect (hope) that this may be because of new functionality in the Perforce API :-)
file://Raymond.