Kam

Merge current REST work into master
Yes - good point. How bout 
"by providing a command line argument which specifies a config file to load (eg -Dconfig.file=<path>/cfg.conf) or even by specifying individual properties on the command line (eg: -D<property>=<value>)."
Or I can just remove this if preferred.


On Wednesday, August 6, 2014 1:43 PM, Sean Owen <notifications@github.com> wrote:
 


In README.md:
> @@ -106,6 +106,10 @@ state in memory. It exposes an HTTP
>  [REST](http://en.wikipedia.org/wiki/Representational_state_transfer) API on top of methods 
>  that query the model in memory. There will be many of these deployed for scale. Each may 
>  also accept new data and write it to Kafka where it can be seen by all Speed layers.
> +The serving layer defaults are provided by a reference.conf. Applications are expected to provide their 
I just mean that there's not a need to qualify it as only pertaining to the serving layer. It's true, and for everything in the project.
—
Reply to this email directly or view it on GitHub.