The other issue is error responses. In the apps I work on we have specific
XML or JSON result formats for application errors, which means the Flex app
must handle those responses differently. If the service is using HTTP header
error responses instead I believe the Flex app can't see them, though I
forget the details.

I assume you've seen this thread:

http://stackoverflow.com/questions/153420/is-it-feasible-to-create-a-rest-client-with-flex


On Thu, Sep 3, 2009 at 3:52 AM, claudiu ursica <[email protected]>wrote:

>
>
> If your Rest API is exposing XML you won't be needing any additional
> libs... the HTTPService class will do just fine ...
>
> C
>
> ------------------------------
> *From:* Haykel BEN JEMIA <[email protected]>
> *To:* [email protected]
> *Sent:* Thursday, September 3, 2009 1:45:11 PM
> *Subject:* Re: [flexcoders] Flex and REST
>
>
>
> Anyone tried one of these libs?
>
> http://code. google.com/ 
> p/as3httpclient/<http://code.google.com/p/as3httpclient/>
> http://code. google.com/ p/as3httpclientl 
> ib/<http://code.google.com/p/as3httpclientlib/>
>
> They seem to support all required http verbs.
>
> Haykel Ben Jemia
>
> Allmas
> Web & RIA Development
> http://www.allmas-tn.com
>
>
>
>
> On Wed, Sep 2, 2009 at 12:55 PM, DannyT <danmo...@googlemail 
> .com<[email protected]>
> > wrote:
>
>>
>>
>> Can anyone give me the definitive answer to whether you can build REST
>> based apps with Flex? There seems to be an incredible amount of FUD about
>> the topic and whilst I appreciate it might not be supported in it's purest
>> form I need to know what is involved in supporting a full REST
>> implementation.
>>
>> I have no experience with REST but we're in the position that a client is
>> going to implement a RESTful service for us to build a Flex application
>> against. If it will 'just work' then great, if not I need to educate them as
>> to any considerations/ workarounds necesscary on the service side of things.
>>
>> Can anyone offer any advice?
>>
>> Cheers,
>> Dan
>>
>> --
>> http://danny-t.co.uk
>>
>
>
>  
>

Reply via email to