file.README.html #11 

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>
  File: README
  
    &mdash; Documentation by YARD 0.8.7.6
  
</title>

  <link rel="stylesheet" href="css/style.css" type="text/css" charset="utf-8" />

  <link rel="stylesheet" href="css/common.css" type="text/css" charset="utf-8" />

<script type="text/javascript" charset="utf-8">
  hasFrames = window.top.frames.main ? true : false;
  relpath = '';
  framesUrl = "frames.html#!file.README.html";
</script>


  <script type="text/javascript" charset="utf-8" src="js/jquery.js"></script>

  <script type="text/javascript" charset="utf-8" src="js/app.js"></script>


  </head>
  <body>
    <div id="header">
      <div id="menu">
  
    <a href="_index.html">Index</a> &raquo; 
    <span class="title">File: README</span>
  

  <div class="noframes"><span class="title">(</span><a href="." target="_top">no frames</a><span class="title">)</span></div>
</div>

      <div id="search">
  
    <a class="full_list_link" id="class_list_link"
        href="class_list.html">
      Class List
    </a>
  
    <a class="full_list_link" id="method_list_link"
        href="method_list.html">
      Method List
    </a>
  
    <a class="full_list_link" id="file_list_link"
        href="file_list.html">
      File List
    </a>
  
</div>
      <div class="clear"></div>
    </div>

    <iframe id="search_frame"></iframe>

    <div id="content"><div id='filecontents'>
<h2 id="label-Helix+Web+Services+-28HWS-29">Helix Web Services (HWS)</h2>

<p>Please note this is <strong>alpha</strong> software.</p>

<p>Helix Web Services creates a series of service APIs exposed via web
technologies, such as HTTP and WebSocket.</p>

<p>Official deployment and documentation is in progress.</p>

<h2 id="label-Architectural+Overview">Architectural Overview</h2>

<p>The core of Web Services is a single Ruby HTTP web application server. The
main server is a Sinatra modular project, that mounts many other services,
also implemented as Sinatra modular projects. Services can be implemented
as generic Rack middleware, we just use Sinatra for the most part.</p>

<p>Access to the Perforce server should be isolated to the core
<code>perforce</code> service.</p>

<p>Each service has access to using a locally running PostgreSQL server for
caching data that can be indexed in interesting ways. There is one
PostgreSQL DB in use - web_services - for the purposes of caching.</p>

<p>Background processes are used as well. These are Sidekiq workers. Redis is
used as the queuing engine binding these together.</p>
</div></div>

    <div id="footer">
  Generated on Mon Oct 12 22:20:49 2015 by
  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
  0.8.7.6 (ruby-2.2.3).
</div>

  </body>
</html>
# Change User Description Committed
#11 16275 Doug Scheirer Merge from main
#10 16196 Doug Scheirer Merge from main
#9 16148 Doug Scheirer Merge from main
#8 16114 Doug Scheirer Merge from main
#7 16079 Doug Scheirer Merge from main
#6 16014 Doug Scheirer Merge down from main
#5 15884 Doug Scheirer Merge from main
#4 15868 Doug Scheirer Merge from main
#3 15845 Doug Scheirer Integ from main
#2 15715 Doug Scheirer merge changes from main
#1 15688 Doug Scheirer Populate -o //guest/perforce_software/helix-web-services/...
//guest/doug_scheirer/helix-web-services/....
//guest/perforce_software/helix-web-services/main/build/doc/helix_web_services/file.README.html
#32 15676 tjuricek HWS/NOARCH/2015.1.main/201509092205
#31 15589 tjuricek Update path to test output and update docs.
#30 15542 tjuricek Add spaces to our basic 'component encode' mechanism, and use it for HVE project IDs.

In general, this will make the HVE IDs a bit more readable.
#29 15517 tjuricek Do not require changelist ID for submitting Helix Sync pending changelists.
#28 15499 tjuricek Naive implementation of helix sync project submit for "helix versioning engine projects".
#27 15487 tjuricek Add basic ability to create pending changelists for helix sync projects.
#26 15479 tjuricek Added a basic "HVE project" implementation for creating clients.
#25 15447 tjuricek Add simple Example application to list "projects" in a HVE instance.

Qt's a little weird to follow, so I may have to find a different kind of example to write. It does work, however.
#24 15240 tjuricek Set api level via request path on all Helix Versioning Engine methods.

This will allow migration of applications to different P4D versions. Our internal methods (like project API) should attempt to handle backward compatibility similarly.

P4WEBAPI-118
#23 15228 tjuricek Revise triggers implementation, tests, and documentation.
#22 15227 tjuricek Revise implementation, tests, and documentation for protections management.

Remove some specs I will not be revising from the helix_web_services project.
#21 15225 tjuricek Revise counter implementation, tests, and documentation

Wasn't available in the Ruby client before, so, it's now available.
#20 15222 tjuricek Revise server specs testing and documentation.

Note: also fixed issues with setting P4PORT via headers. For whatever reason, the host setting doesn't seem to work like I expect it to, though P4PORT works just fine.
#19 15211 tjuricek Implement tests and documentation for label spec management.
#18 15210 tjuricek Implement tests and documentation for job spec management.
#17 15209 tjuricek Implement tests and documentation for group spec management.
#16 15208 tjuricek Revise 'command' implementation, tests, and documentaiton.

This includes a change from a command blacklist to a whitelist. See P4WEBAPI-21
#15 15205 tjuricek Implemented tests and documentation for depot spec editing.
#14 15189 tjuricek Update files implementation, testing, and documentation.
#13 15185 tjuricek Update user spec management implementation, tests, and documentation.
#12 15144 tjuricek Setup stream spec tests and documentation.

Also revised the documentation folder http_p4_web_api -> helix_versioning_engine
#11 15132 tjuricek Provde a basic submit -e mechanism on classic perforce workspaces.
#10 15110 tjuricek Revise changes methods for new p4 connection handling, add server specs, remove model references in client, and update asciidoc documentation.
#9 15099 tjuricek Revise project services to be our simple 'container' for other systems.
#8 15098 tjuricek Revised project services to GET-only forms.

With Helix Sync revising to integrate purely with Helix Cloud, this is the only thing we can reasonably define.
#7 15090 tjuricek Update _proposed_ API for project services.

This is *very likely* to change, and will not be implemented until reviewed.
#6 15078 tjuricek clients spec method revisions

Updated some other documentation.
#5 15077 tjuricek Add new 'model' technique, revised branch spec operations, test Auth::Middleware.

The Ruby client now does *not* strictly type anything, but extends OpenStruct with helper methods to help deal with inconsistent data formats.
See the OpenModel class documentation for more details.

The Auth::Middleware class is also *finally* implemented as well. This does not take into account all possible variations of server behavior (yet), but that will happen in follow-up work.
#4 15073 tjuricek Update Auth::Middleware and add spec
#3 15053 tjuricek Revise the client API to use the new login method.

The current specs will need to be revised since data normalization is moving out of the server and into the client.
#2 15038 tjuricek Document 'login' auth method and client programming overview.
#1 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.