[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Versioning of LIBHTTP
Hi Scott,
I am glad to have you. Well my program is running fine for about a month and suddenly without any change on my source code or server, it start to malfunctioning. I used to get values for my 'ShorText' and 'Indgrosdet' variables. But now when I debug my function mapMaterialGetDetail, I noticed that the scans brings back 5 odd variables names with blanks as values as shown below:
n0:MessageID
n1:Action
soap-env:Header
soap-env:Body
soap-env:Envelope
Since the function is running without any problem I did get a ReturnCode = 1. So I ended with no errors and nothing for my variables 'ShorText' and 'Indgrosdet'
-----Message d'origine-----
De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Scott Klement
Envoyé : lundi 11 juillet 2011 17:04
À : ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Objet : Re: Versioning of LIBHTTP
Hi William,
Unfortunately, I really don't understand enough of your question to help
you.
You seem to be telling me that HTTPAPI shouldn't be returning 1, it
should be returning something else. Okay, let's go with that...
What should it be returning? And under which circumstance?
Can you post an HTTPAPI debug log (httpapi_debug.txt) that shows the
situation in which it's malfunctioning? Preferably with a description
of what HTTPAPI should do differently?
On 7/11/2011 2:56 PM, Ha, William wrote:
>
> My returnCode is a 1. So there is no error for the call. I can see
> the odd returning variables names thru a Debug session. I get my
> variables in a standard procedure as below:
>
> ReturnCode =
> http_post_xml( Http_Addrs
> : %Addr(Soap) + 2
> : %Len(Soap)
> : *NULL
> : %Paddr(mapMaterialGetDetail)
> : %Addr(MaterialGetDetail)
> : HTTP_TIMEOUT
> : HTTP_USERAGENT
> );
>
> // Verify for errors
> Select;
> // Time out
> WHen (ReturnCode = 0);
> Eval ErrMsg = %Trim(Message(07));
> // Error exist
> WHen (ReturnCode<> 1);
> Error = Http_error();
> // Show a formatted message to the user in case of 500 message
> If %Scan('HTTP/1.1 500' :Error) = 0;
> Eval ErrMsg = %Trim(Message(06)) + ' ... ' + %Trim(Error);
> EndIf;
> EndSl;
>
> P mapMaterialGetDetail...
> P B
> D PI
> D GetDetail LikeDs(MaterialGetDetail)
> D Depth 10I 0 Value
> D Name 1024A Varying Const
> D Path 24576A Varying Const
> D Value 32767A Varying Const
> D Attrs * Dim(32767) Const Options(*Varsize)
>
> * Local variables
> D* None
>
> /free
>
> // Parse return data for ZMaterialGetDetail
> Select;
> When Name = 'ShortText';
> Eval GetDetail.O_ShortText = Value;
> When Name = 'Indgrosdet';
> Eval GetDetail.O_GrosDetail = Value;
> EndSl;
> /End-free
>
> P mapMaterialGetDetail...
> P E
>
>
> -----Message d'origine-----
> De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Mike Krebs
> Envoyé : lundi 11 juillet 2011 15:46
> À : HTTPAPI and FTPAPI Projects
> Objet : RE: Versioning of LIBHTTP
>
> Scott had done a pretty good job of retaining compatibility. If you want to jump to latest (even latest Beta-very stable), you should be fine.
>
> Are you sure you didn't get an error from the server? Maybe you didn't get a communication error but it looks oddly like you pulled some error information in the return fields. Where did you find "some variables"? Are you ignoring the return codes in your programs? Are you keeping a log of the sent/received data?
>
> *************************************************
> Hi all,
>
> I want to know if each version of LIBHTTP is backward compatible. I am using right now the version 1.23. It is working fine up to a few days ago. And suddenly without any modifications on my source codes, one of my call to the procedure http_post_xml did not return all the parms that I am supposed to get. Instead of that I got without any error, some variables like below:
>
> n0:MessageID
> n1:Action
> soap-env:Header
> soap-env:Body
> soap-env:Envelope
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------