Form Encytype

[sheavalentine-mdsol]

We need way a way of specifying how to encode the request body.

See: http://www.w3schools.com/html/html5_form_attributes.asp

default: formenctype="multipart/form-data"

Probably not calling it formenctype. Open question.

[ChazzMaTazz]

Hi Shea, We do use a format in the iMedidata
http://developer.imedidata.com/desktop/Overview/Your_HTTP_Request.htm,
Designer
Web Services
http://designer-ws-webhelp.s3.amazonaws.com/WebHelp_HTML5/desktop/Overview/Your_HTTP_Request_and_Response_Message_Headers.htm,
and Rave Web Services
http://rws-webhelp.s3.amazonaws.com/WebHelp_ENG/index.html portals. Are
these helpful? I'd appreciate feedback, as we will eventually document for
external users the Hypermedia resources. I'll use any updates/suggestions
that you make to improve our documentation.

Many thanks and best wishes, Charles

On Tue, Jul 8, 2014 at 11:40 AM, Shea Valentine [email protected]
wrote:

We need way a way of specifying how to encode the request body.

See: http://www.w3schools.com/html/html5_form_attributes.asp

default: formenctype="multipart/form-data"

Probably not calling it formenctype. Open question.

—
Reply to this email directly or view it on GitHub
#8.

[sheavalentine-mdsol]

I'm confused by my own comment. Isn't this covered here?
https://github.com/mdsol/hale#44-enctype

[sheavalentine-mdsol]

Okay, I think I'm going to add a request_enctype. Meaning, here is a link, you may request that the service give you back data in the following formats.

[sheavalentine-mdsol]

Or maybe jus media_type

[fosrias]

How about body_enctype? media_type might work, but not as explicit and one
might wonder the difference between enctype. Might want to look at UBER or
verbose along these lines for a little inspiration. ;)

On Thu, Jul 17, 2014 at 10:00 AM, Shea Valentine [email protected]
wrote:

Or maybe jus media_type

—
Reply to this email directly or view it on GitHub
#8 (comment).

[sheavalentine-mdsol]

Resolved with "request_encoding"

[fosrias]

@sheavalentine-mdsol Maybe you could past thee commit hash or pr that does it here and close this issue then.

[sheavalentine-mdsol]

I didn't understand that sentence.

[fosrias]

Ha. You don't understand pidgeon typing?

Option A: I was saying, maybe you just find the pull request that resolved this, or the individual commit where the changes were made that resolved this issue into a comment here and close. Then the closed issue will have a reference to what actually changed.

Option B: Just close this if it is resolved.

[sheavalentine-mdsol]

I think it's introduced in the open PR

[fosrias]

Ok. I think if you paste:

Closes #8

into the comment of the open PR, it will close this issue and create the
relation between the PR and the issue for you when the PR is merged.

On Fri, Aug 22, 2014 at 10:31 AM, Shea Valentine [email protected]
wrote:

I think it's introduced in the open PR

—
Reply to this email directly or view it on GitHub
#8 (comment).