Re: http_url_post_xml and REST

The example in their documention is a php derived sample. I'm just having one of those moments where I'm not connecting the dots again:





<?php

$urltopost = "https://[ServerName]/orders/api/add_order";;

$datatopost = array (

"code" => "[YOUR CODE]",

"api_key" => "[YOUR KEY]",

"data" => file_get_contents("import.xml"),

);





I have the XML created and am at the point to send it over, but am not really sure how to connect them. The XML file is a pretty good size (190k) and has the potential to be a lot larger on some occasions.



To me, it all looks like a regular everyday POST, but with file_get_contents made me think I probably should go the same route because of the file sizes.



The documentation keeps going on about REST, but I don't see anything unusual about any of the above...





----- Original Message -----


From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, July 9, 2013 3:25:33 PM
Subject: Re: http_url_post_xml and REST

Hello,

In what format would you like to do this?   a POST request allows one
"request body" (basically, a stream of bytes to upload).  In that body,
you can send a raw file, such as an XML file, or you can use some sort
of transfer encoding that allows you to put multiple pieces of data
together.

XML itself is sometimes used for that.   Other methods include
multipart/form-data encoding, or the traditional web format of
application/x-www-form-urlencoded  (which is unusual with web services,
but not unheard of.)   JSON is also sometimes used for this.

Do you know more about the format of the request body you need to send?

-SK



On 7/9/2013 2:08 PM, tegger@xxxxxxxxxxx wrote:

I have a project that I need to be able to post a rather large XML
file to a web service.

I've looked around for an example to follow that will post the XML
from the IFS and include some basic information on the actual POST.
(In this particular case, I have to post strings that ID our system
to the remote. Kinda of like a user ID/password).

Has anyone tripped across a good example?