RestRserveRequest methods about restrserve HOT 5 CLOSED

Sure. Major changes require more testing and review.
parse_request now used only in http_request. parse_request now used as preconstructor for the RestRserveRequest. I have not any reasons to hold this in the separate functions which wrap one another.

from restrserve.

I will plan move parse_request to RestRserveRequest constructor.

• cookies field.
• request_id must be moved to the active bindings to protect it.
• set_param/has_param/delete_param for the query.
• set_header/has_header/delete_header for the headers.
• set_cookie/has_cookie/delete_cookie for the cookies.
• set_body
• set_content_type
• accept field.
• encoding field.

from restrserve.

I will plan move parse_request to RestRserveRequest constructor.

Not sure about that. But you can try to propose something. Just keep development of this particular feature in a separate branch, so we can proceed with the rest of functionality independently.

from restrserve.

Should we rename query public field to params?

from restrserve.

If an HTML form is POSTed to the API using the application/x-www-form-urlencoded media type, Falcon can automatically parse the parameters from the request body and merge them into the query string parameters.

from restrserve.