Hi,
> -Latest analytics include a little less than 2000 hits per day on the
> website during the work week (less on weekends).
It’s dropped a little (only one day a week over 2000 hits)
> -There were more than 6000 installs of Apache Flex 4.14.1 since its
> release about two months ago.
Now
Hi,
I am currently working on a fun project in which we are having a little battle
of the client technologies. The backend server is a REST service communicating
in JSON.
While my Flex client is currently way beyond the others, I just stumbled over a
problem which I don't quite know how to
This is a restriction of the native http client within AFP stack (Flash
Player and AIR). It only supports POST and GET.
The work-around is to use a 3rd party HTTP client within your app.
Essentially, a client that builds its own HTTP header and then passes it
along. There are quite a few
I believe you can solve this by proxying the calls through Javascript,
using ExternalInterface as well.
Thanks,
Om
On Sep 7, 2015 6:45 AM, "Krüger, Olaf" wrote:
> Hi,
> I ran into the same problem, here's a (very old) summary of the problem:
>
Hi,
I ran into the same problem, here's a (very old) summary of the problem:
http://verveguy.blogspot.de/2008/07/truth-about-flex-httpservice.html
I've found these workarounds:
1) Using " X-HTTP-Method-Override" (Server side must support this):
I believe Socket based HTTP Clients can do this. There’s a couple out there.
[1][2].
The author of the first seems to recommend the second.[3]
[1]https://code.google.com/p/as3httpclient/
[2] https://github.com/gabriel/as3httpclient
Sorry -- didn't notice that it was cc'ed to more than one mailing list.
-Nick
On Mon, Sep 7, 2015 at 3:56 PM, OmPrakash Muppirala
wrote:
> Nick responded a couple of days ago. You are probably not subscribed to
> the mailing lists. Here is his response:
>
> In 4.14, we
Nick responded a couple of days ago. You are probably not subscribed to
the mailing lists. Here is his response:
In 4.14, we updated the mobile skins to look closer to the default skins
provided by the OS. We did include a compiler option that will bring back
the old default.
More
Well I solved my problem by using Springs HiddenHttpMethodFilter
This monitors incoming requests for "_method" parameters and allows to override
them. So I was able to fake a PUT by adding "?_method=PUT" and a DELETE by
adding "?_method=DELETE" to my rest url ... it's not nice, but it works.
The problem with socket based http clients are that they bypass the browser
completely and hence the browser cache. It hits you really for those GETs
you want cache working for.
Thanks,
Om
On Sep 7, 2015 10:16 AM, "Harbs" wrote:
> I believe Socket based HTTP Clients can
10 matches
Mail list logo