== HTTP Protocol Reference Each section includes methods related to a particular topic or resource. === P4 Web API HTTP Protocol The P4 Web API is our HTTP based abstraction on top of core Perforce server concepts. Most Perforce command methods are represented here. The main difference is that commands that rely on client workspaces, which includes a lot of the 'manipulation' commands. - <<_p4_web_api_branches_http_protocol>> include::http_p4_web_api/branches.asc[] Changes Read and create changelists Clients List and manage client specifications Commands Execute generic Perforce methods Depots List and manage depot specifications Files File browsing and upload methods. Groups List and manage group specifications Jobs List and manage job specifications Labels List and manage label specifications Protections List and update system protections Servers List and manage server specifications Sessions Manage a Perforce Web API security token Triggers List and update system triggers Users Manage Perforce users
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 15038 | tjuricek | Document 'login' auth method and client programming overview. | ||
#4 | 15032 | tjuricek |
Starting config and doc revisions. System is now broken while revisions underway. Configuration of the p4d connection is now done via a single HWSSettings middleware object injected into the Rack env. The HWSP4Cleanup middleware now cleans up any p4 injected into the Rack env. The Auth::App class now mostly just contains one method to generate a p4 ticket. /auth/v1/login. Added yard documentation for the main project. Yard docs have been reconfigured to dump into build/ directories. This should probably be done with each release. Hm... The top level rake file contains a task, 'all:doc', to update our documentation. This should probably be run for each checkin. Hm... Specs are now using Rack::Test on top of a 'live' p4d. I'd suggest you still use the p4util mechanism, which now dumps to a /tmp folder, so we can safely add P4IGNORE rules back into your local .p4config file. Old 'perforce' application now called 'helix_versioning_engine'. Removing cache data. Helix Sync may be slow. It may also get axed. We'll see. |
||
#3 | 14182 | tjuricek | Asciidoc conversion of the changes HTTP guide | ||
#2 | 13612 | tjuricek | Update deployment guide, switch built documentation to asciidoc, remove unused packaging script for p4_web_api | ||
#1 | 13555 | tjuricek |
Starting Asciidoc conversion of documentation. Removed the "Shared Quality" document, that basically is online now at: https://confluence.perforce.com:8443/display/PWS/Quality+Assurance Adding some topology graphviz images used for online documentation. |