I am trying to create a restful webservice that will accept a “post” method and have IS act as the server of this webservice.
I understand the concept of the get method were the $resourceID is part of the URL and have created several get webservices, I also understand how to use the $path and other optional paramaters with the ?name=value&… all within the URL, however if there are 25 different name-value pairs that have to be supplied for a “post” I wouldn’t think you would code these all within the URL to execute, you would instead include this data within the request header such as in the example given in the REST Developer’s guide 8.2.
Documentation for the Discussion example might provide the following examples to illustrate body structure: [FONT=Palatino Linotype,Palatino Linotype][SIZE=3][FONT=Palatino Linotype,Palatino Linotype][SIZE=3]Example 1: Creating a new topic
[FONT=Letter Gothic MT,Letter Gothic MT][SIZE=1]POST http://IS_server:5555/discussion/topic
Content-Type: <application/x-www-form-urlencoded; utf-8>
[/SIZE][/FONT]Response: If the request was valid, the Discussion application will respond with the following
[FONT=Letter Gothic MT,Letter Gothic MT][SIZE=1]HTTP/1.1 201 Created
ETag: 32619Location: http://host/discussion/topic/32619
How do I retrieve the request headers and extract out all of the “topic” information that would be need to create a new topic if there are 25 different “pairs” of information?[/SIZE][/FONT]