> -----Original Message-----
> From: Victor Johnson [mailto:Victor_Johnson@xxxxxxxxxxxx]
>
> William I. writes:
>
> > There are some simple scripts you can create that help.
> > (Simplest is to compare your "have" list with the files on
> > the system - that at least tells you if a file is
> > missing.) Also, if connection speed is an issue, a local
> > proxy server (p4p) can help; it will cache unchanged
> > files for quick access. -Wm
>
> Yes, & that is what I'm in the process of doing. However,
> when one must supplement missing native functionality by
> employing/maintaining custom scripts and wrappers, that is
> prima facia evidence of a "drawback", no? Our GUI based
> users, particularly the documentation tech writers, aren't
> fond of command line tools in order to build their change
> lists which may number in the many thousands of files.
P4Win does provide some of that functionality depending
on the view settings.
> We do make use of a proxy but [if my admittedly newly
> acquired knowledge of Perforce is correct] when the
> client must request information that resides in the
> server metadata, the proxy is a mere pass-through and
> doesn't add any performance benefit?
We haven't seen performance issues related to metadata,
only in file transfers (which the proxy helped solve).
Metadata is a small burden. (Not every command requires
it to be passed to the client, either, of course. Your
example of syncing to "have" shouldn't - it's the server
that reads the have list, not the client.) -Wm
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
