We use HTTPService for all of our server data calls. There were a few
modifications we used. We use E4X for the data format, having the server side
send all responses in XML. When a response is sent back from the server we
have a success message that is stored in a status node.
So the c
s that I had to change the rpc package of the
flex sdk.
hope that this is useful to someone!
[1] https://gist.github.com/davidcoleman007/4717928
Cheers!
-Dave
> From: dnai...@emarketinginc.com
> To: dev@flex.apache.org
> Date: Tue, 5 Feb 2013 14:16:54 -0700
> Subject: RE: H
From: Rick Winscot [mailto:rick.wins...@gmail.com]
Sent: Tuesday, February 05, 2013 10:58 AM
To: dev@flex.apache.org
Subject: Re: HTTPService Response Headers
Dan.
If you are not using a proxy service like BlazeDS... anything other than an
HTTP200 is going to cause your Flex application fits.
server you send a 500, triggering the flex IOError, then you include in the
> text some JSON or other info that describes the error condition. This
> allows you to know that a 200 is ONLY good data (short of a total server
> meltdown).
>
> From: david_coleman_...@hotmail.com
> To: de
then you include in the text some JSON or
other info that describes the error condition. This allows you to know that a
200 is ONLY good data (short of a total server meltdown).
From: david_coleman_...@hotmail.com
To: dev@flex.apache.org
Subject: RE: HTTPService Response Headers
Date: Tue, 5 Feb
ested. (it may not be a
perfect patch, and to meet Apache standards it probably should be polished, BUT
it works and is used by thousands of ppl in an air app running on sdk 4.6.0).
> Date: Tue, 5 Feb 2013 12:57:42 -0500
> From: rick.wins...@gmail.com
> To: dev@flex.apache.org
> Subject
Dan.
If you are not using a proxy service like BlazeDS... anything other than an
HTTP200 is going to cause your Flex application fits. If you are looking for
the notion of a 'successful failure' where an operation completed (e.g. a
partial save) but had errors. You'll need to implement the sema
