Adding extension for attachments

how is this handled in HTML and the RFC's you mention. surely this is
covered.


On Sun, Oct 12, 2014 at 2:10 PM, Glenn Block <notifications@github.com>
wrote:

> In attachment.md:
>
> > +--AaB03x
> > +content-disposition: form-data; name="email"
> > +content-type: text/plain; charset=us-ascii
> > +jdoe@example.org
> > +--AaB03x
> > +content-disposition: form-data; name="avatar"
> > +content-type: image/jpeg
> > +...
> > +--AaB03x
> > +```
> > +## Receving attachments
> > +A client may also receive a response that contains attachments. In these cases the response media type will be "multipart/mixed" containing parts for a collection+json document as well as attachments.
> > +
> > +### Parts
> > +* The first part in the document will be a CollectionJson document. The document will contain pointers back to the attachments in the response.
> > +* All _attachment_ fields in the data element must have a value set to the name in the content-disposition header of the corresponding part.
>
> This is a good question. One way to handle this would be to add "Name" as
> a property of the disposition header. This way the name can be unique, but
> the filenames are the same. I originally had this but removed it as it
> seemed redundant. Open to ideas here.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/collection-json/extensions/pull/7/files#r18748977>.
>