initial commit

Attempted to setup a basic architecture that could work across frameworks and
formats.

Intended as a discussion starter!
I am not against reader/writer as there is StreamReader and StreamWriter.
Just questioning why it is needed. The underlying content is a raw stream,
which is why I asked the question.
On Wed, Dec 3, 2014 at 9:34 AM Geoffrey Braaf <notifications@github.com>
wrote:

> In
> src/DotNetHypermedia/DotNetHypermedia.CollectionJson/CollectionJsonSerializer.cs:
>
> > @@ -0,0 +1,23 @@
> > +﻿using System;
> > +using System.IO;
> > +
> > +namespace DotNetHypermedia.CollectionJson
> > +{
> > +    public class CollectionJsonSerializer : IResourceSerializer<CollectionJsonResourceObject>
> > +    {
> > +        public void Serialize(TextWriter writer, CollectionJsonResourceObject resource)
>
> Hmmm, not 100% sure. :)
>
> I'm currently working on some export code for a consulting gig where we
> extensively use TextWriter. Also, if you look at the Json.NET specific
> converters (in f.ex. WebApi.HAL) they also append to a writer. Concluding,
> it just felt natural.
>
> I do feel that a writer is more explicit than a stream, as consuming code
> cannot do any reading or other things to the ResponseStream (because that
> is what it is essentially).
>
> It does make for simple unit/approval-testing imho.
>
> Let me flip the question though, why use the Stream directly?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/DotNetHypermedia/DotNetHypermedia/pull/15/files#r21248740>
> .
>