Cloudant query support

Added code to create a simple index with integration tests using Cloudant query API #53. Before adding more features, wanted to have a quick review of the components. We don't have querying yet. If okay, will add delete/listing of indices, followed by query.
Actually, I need some clarity around where to use this over or in addition
to the other one.
Both of them get passed as ISerlaizer instances. Are they required for APIs
where we support strongly types entities in return (i.e. where we can use
MaterializeSuccessfulResponse<TIncludedDoc> with TIncludedDoc as something
other than string?
I was able to return a strongly typed entity in a test (the test
Query_can_skip_and_limit_results in the file QueryTests.cs does it.

I saw this getting used in generating requests where we serialize Json docs
into querystring parameters. Should we use it for find API (there are cases
where we use into Serializer.ToJson or ToJsonArray)?

On Fri, Dec 19, 2014 at 3:02 AM, Daniel Wertheim <notifications@github.com>
wrote:
>
> In source/projects/MyCouch.Cloudant.Net45/Contexts/Queries.cs
> <https://github.com/danielwertheim/mycouch/pull/54#discussion-diff-22073017>
> :
>
> > +using MyCouch.Serialization;
> > +using System.Net.Http;
> > +using System.Threading.Tasks;
> > +
> > +namespace MyCouch.Cloudant.Contexts
> > +{
> > +    public class Queries : ApiContextBase<IDbClientConnection>, IQueries
> > +    {
> > +        protected PostIndexHttpRequestFactory PostIndexHttpRequestFactory { get; set; }
> > +        protected GetAllIndexesHttpRequestFactory GetAllIndexesHttpRequestFactory { get; set; }
> > +        protected DeleteIndexHttpRequestFactory DeleteIndexHttpRequestFactory { get; set; }
> > +        protected FindHttpRequestFactory FindHttpRequestFactory { get; set; }
> > +        protected IndexResponseFactory IndexResponseFactory { get; set; }
> > +        protected IndexListResponseFactory IndexListResponseFactory { get; set; }
> > +        protected FindResponseFactory FindResponseFactory { get; set; }
> > +        public Queries(IDbClientConnection connection, ISerializer serializer)
>
> Shall this only take one serializer? Should it not also take the "Document
> configured serialzer" for use in e.g. FindResponseFactory? Look at
> Searches and the SearchIndexResponseFactory.
>
> You don't need to change. Just let me know.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/danielwertheim/mycouch/pull/54/files#r22073017>.
>