== About This Manual This guide covers administering and developing against the Helix Web Services. Helix Web Services provide common services and APIs that interact with the Helix Versioning Engine. A Helix Web Services server is a web server, and it's APIs are fundamentally based on the HTTP protocol. Not all aspects of the Helix Versioning Engine are provided by Helix Web Services, vice versa. Some services provided by Helix Web Services are not available in the Helix Versioning Engine. === Please give us feedback If you have any feedback for us, or detect any errors in this guide, please email details to manual@perforce.com.
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 17323 | tjuricek |
Revise the documentation to use the JVM-based asciidoctor. This will generate the DocBook XML. I'm still ironing out exactly what the CD process is here. |
||
#3 | 17228 | tjuricek |
Revising configuration, removing clearly obsolete variables, and renaming some for consistency. Some variables need to remove underscores, because those underscores are actually not really a good idea for HTTP headers. (Some servers block those values as keys, depending on config.) |
||
#2 | 17090 | tjuricek |
Revised documentation based on edits received (on paper). Removed Helix Web Services ruby client references, since there is no publication plan for this API. |
||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/doc/00_preface.asc | |||||
#2 | 14980 | tjuricek |
Starting to make revisions to the Asciidoc guide. These are just revisions to the preable sections. |
||
#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. |