Hi Chuck,

Sorry I dropped out of the conversation, but I had a 2 hour conference call to 
do. 

Posting to a webservice in this manner is not what is considered good practice, 
but that doesn't mean it'll stop people from trying of course. This looks like 
something from the early days of XML over HTTP, before people knew how to spell 
XML 8-\ 

Have you tried taking the "&xml=" argument out of the URL string, and supplying 
it as a separate post argument anyway? Use the POSTARGS= attribute of @URL 

You never know, their system might treat GET and POST arguments agnostically, 
just like @ARG does? 

The bit of documentation you posted doesn't appear to state a "GET" HTTP method 
specifically, so try the above. 

But of course, even if it does work there is no quarentee their system will 
necessarily accept multiple "HotelAvailabilityListQuery" elements. 

You might be stuck with looping your <@URL> call for each hotel. 

Sorry, not much help I guess. Good luck.

Scott,


On Friday, February 8, 2008 1:25pm, Chuck Lockwood <[EMAIL PROTECTED]> said: 

> Robert,
> 
> 
> 
> I pasted that xml in from their example.  I understand the "one liner", 
> thanks!
> 
> 
> 
> It is definitely the length of the GET that's causing the problem.  I can 
> reliably recreate it by sending 2000+ character packets.
> 
> 
> 
> Of course this problem arises the Friday before a Monday site launch, just 
> my luck!  So I guess the client can only book one hotel room at a time until 
> I figure out a solution..
> 
> 
> 
> Chuck Lockwood
> 
> President
> 
> 
> 
> 
> ............................................
> 
> 309 Main Avenue
> Hawley, Pa 18428
> (P) 570.226.7340 
> (F) 570.226.7341
> 
> www.lockdata.com <http://www.lockdata.com/>
> 
> 
> 
>   _____
> 
> From: Robert Garcia [mailto:[EMAIL PROTECTED] 
> Sent: Friday, February 08, 2008 11:14 AM 
> To: [email protected] 
> Subject: Re: Witango-Talk: <@URL> + XML
> 
> 
> 
> That xml is not going to work in a get argument. must be one line, like: 
> 
> 
> 
> <@assign local$xml "<root><node1>data</node1><node2>data</node2></root>"> 
> 
> 
> 
> <@url "http://someurl.com/path/file.php?foo=bar 
> <http://someurl.com/path/file.php?foo=bar&xml=> &xml=<@var local$xml 
> encoding=url>">
> 
> 
> 
> --
> 
> 
> 
> Robert Garcia
> 
> President - BigHead Technology
> 
> VP Application Development - eventpix.com
> 
> 13653 West Park Dr
> 
> Magalia, Ca 95954
> 
> ph: 530.645.4040 x222 fax: 530.645.4040
> 
> [EMAIL PROTECTED] - [EMAIL PROTECTED]
> 
> http://bighead.net/ - http://eventpix.com/
> 
> 
> 
> On Feb 8, 2008, at 8:02 AM, Chuck Lockwood wrote:
> 
> 
> 
> 
> 
> Hi Scott,
> 
> 
> 
> Well, they don't tell me much. This is hotels.com, so there has to be a lot 
> of people that get it to work.
> 
> I found this so far: 
> 
> All requests (except Reservations) made to TravelNow.com should be made to 
> the following URL: 
> http://www.travelnow.com/external/xmlinterface.jsp?cid=x 
> <http://www.travelnow.com/external/xmlinterface.jsp?cid=x&;> & 
> resType=hotel200631&intfc=ws&xml=z
> 
> Reservation requests MUST be made to this secure URL: 
> https://www.travelnow.com/external/xmlinterface.jsp?cid=x 
> <https://www.travelnow.com/external/xmlinterface.jsp?cid=x&;> & 
> resType=hotel200631&intfc=ws&xml=z
> 
> * parameter x is equal to the IAN affiliate ID assigned to your 
> account 
> * parameter z is equal to the XML data TravelNow.com is responsible 
> for processing.
> 
> http://www.travelnow.com/external/xmlinterface.jsp?cid=1&resType=hotel200631 
> &intfc=ws&xml=<HotelSessionRequest method='runHotelAvailabilityListQuery'> 
> <HotelAvailabilityListQuery> 
> <city>New York</city> 
> <stateProvince>NY</stateProvince> 
> <country>US</country> 
> <arrivalDate>08/31/2006</arrivalDate> 
> <departureDate>09/02/2006</departureDate> 
> <RoomGroup>
>    <Room> 
>         <numberOfAdults>2</numberOfAdults> 
>    </Room>
> </RoomGroup> 
> <numberOfResults>25</numberOfResults> 
> </HotelAvailabilityListQuery> 
> </HotelSessionRequest>
> 
> 
> 
> As usual, thanks!
> 
> 
> 
> Chuck
> 
> 
> 
> -----Original Message----- 
> From: Scott Cadillac [mailto:[EMAIL PROTECTED] 
> Sent: Friday, February 08, 2008 10:32 AM 
> To: [email protected] 
> Subject: RE: Witango-Talk: <@URL> + XML
> 
> 
> 
> Hi Chuck,
> 
> 
> 
> Unfortunately there is an unspecified limit to how long you can make a URL. 
> GET requests were never meant to support long strings of data, thus the POST 
> request. People try, but eventually somewhere in the URL's travels a proxy, 
> router or gateway somewhere will start truncating the URL.
> 
> 
> 
> Are you sure you're interpretting the webservice's specs correctly? 
> 
> 
> 
> Do you have any more information you can post?
> 
> 
> 
> Let us know, when you have time.
> 
> 
> 
> Scott,
> 
> 
> 
> 
> 
> 
> 
> On Friday, February 8, 2008 11:23am, Chuck Lockwood <[EMAIL PROTECTED]> 
> said:
> 
> 
> 
>> We are using a webservice that requires that the XML be passed in as a 
> get,
> 
>> not a post argument (so it seems).
> 
>>
> 
>>
> 
>>
> 
>> The below works until the <@ARG testXML> gets over 2000 characters then it 
> 
>> starts getting truncated.  Am I nuts or does witango do this? 
> 
>>
> 
>>
> 
>>
> 
>> <@ASSIGN request$method_response VALUE="<@URL LOCATION='<@ARG 
> 
>> vURL>&xml=<@ARG TestXML>'>">
> 
>>
> 
>>
> 
>>
> 
>> Suggestions?
> 
>>
> 
>>
> 
>>
> 
>> Chuck Lockwood
> 
>>
> 
>> President
> 
>>
> 
>>
> 
>>
> 
>>
> 
>> ............................................
> 
>> 
> 
>> 309 Main Avenue
> 
>> Hawley, Pa 18428 
> 
>> (P) 570.226.7340
> 
>> (F) 570.226.7341 
> 
>>
> 
>> www.lockdata.com <http://www.lockdata.com/>
> 
>>
> 
>>
> 
>>
> 
>> 
> 
>> ________________________________________________________________________ 
> 
>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf 
> 
> 
> 
> ________________________________________________________________________ 
> 
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf 
> 
> 
> 
> 
> 
> ________________________________________________________________________ 
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf 
> 
> 
> 
> 
> 
> ________________________________________________________________________ 
> 
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf 
> 
> ________________________________________________________________________ 
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to