Perhaps  "objects are [generally|usually|ideally|can be] instantiated,
referenced..."  and /s/**PipeConfig**/configuration?

Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.



On Tue, Apr 23, 2013 at 8:49 AM, Kris Borchers <notifications@github.com>wrote:

> In docs/specs/aerogear-client-pipe/index.markdown:
>
> > @@ -0,0 +1,107 @@
> > +---
> > +layout: basic
> > +title: AeroGear Client Content Pipes
> > +
> > +---
> > +
> > +# AeroGear Pipelines and Pipes
> > +
> > +The AeroGear client libraries provide the **Pipe** interface as an abstraction around high latency data sources.  **Pipe** defines several asynchronous methods for performing CRUD operations on a `resource` managed by this source.
> > +
> > +**Pipe** objects are instanciated, referenced, and accessed from the **Pipeline** service.  **Pipeline** consumes a `baseURL`, and a **PipeConfig** object to create a **Pipe**.
>
> I guess it depends on how you read it. A Pipe does not have to be
> "referenced and accessed from the Pipeline service." It can be but that is
> not required once it's created. Also, there is a config object when
> creating a Pipeline (and its Pipes) but it is never explicitly called a
> "PipeConfig". I guess my issue is some of the terms are very specific.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/aerogear/aerogear.org/pull/55/files#r3914785>
> .
>