The document details various aspects of integrating with Perforce, including data sources, command line and API options, and their respective advantages and disadvantages. It also discusses server triggers, broker usage, and the integration of Perforce clients like p4v and Swarm. Additionally, it provides contact information for further questions.

1. 1
Matt Attaway
Open Source Community
Manager
Perforce the Plentiful Platform

2. 2

3. 3

4. 4

5. 5
Perforce Data Sources

6. 6
Perforce Data Sources
§ Standard commands
§ Logtail
§ Journal -> P4toDb
§ Monitor
§ Spec depot

7. 7
APIs

8. 8
Command Line

9. 9
Command Line Advantages
§ Runs Everywhere
§ Output is easily parsed
§ Access to full range of Perforce commands

10. 10
Command Line Disadvantages
§ Performance penalty
§ Must parse text output yourself

11. 11
APIs

12. 12
APIs
§ Perl
§ Python
§ Ruby
§ Objective C
§ PHP
§ Java
§ .Net
§ Node.js
§ C++

13. 13
API Advantages
§ More performant
§ Results parsed into data structures
§ Uses language exception support

14. 14
API Disadvantages
§ Needs to be installed
§ Not all commands available in some languages

15. 15
P4Web

16. 16
Git

17. 17
P4VC

18. 18
Commons Web Services

19. 19
P4DTG

20. 20
Chronicle

21. 21
Integrating with Perforce

22. 22
Integrating with Perforce
Server

23. 23
Server Triggers

24. 24
Server triggers
§ Form
§ Out/Pre/Parsed/Post/Delete
§ Shelve
§ Pre/Post/Delete
§ Archive
§ Commit
§ Pre/Content/Post
§ Fix
§ Add/Delete

25. 25
Server Broker

26. 26
Broker Usage
§ Redirect users to replica servers
§ Deny commands

27. 27
Integrating with Perforce
Clients

28. 28
P4V

29. 29
P4V Extension Points
§ Custom tools
§ Alerts
§ Tabs
§ Submit dialog

30. 30
Swarm

31. 31
Insights

32. 32
Data Storage

33. 33
Data Storage
§ Files
§ File attributes
§ Counters/keys
§ Index/search
§ Properties

34. 34
Questions?
Follow me
Matt Attaway: matt@perforce.com, @p4mataway
P4IdeaX Forums