|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15653) Filter changes by view... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)

Server side filtering would be more efficient in many real cases, such as an integrate to create a new branch, or an automated nightly integrate between branches (we do both): i.e. when you're only interested in a few files from a big changelist. It also means you don't have to implement your own client side filter algorithm which is just duplicating Perforce's own functionality, and a potential home where new bugs can nest![]()
I don't see an advantage to the client side filtering, except that you save a few seconds and some unnecessary traffic on older servers (we use 2011.1 where I could measure no real difference).
From my side, either should be acceptable in practice - but client-side seems like more work for little payback. IMHO better to spend the time adding server version detection (so you can use fstat -T and many other new features) than worry about performance with older versions.