Re: Apache Flex AIR Application problems with a limitation of two HTTP request on windows

Wed, 19 Dec 2018 02:56:08 -0800

I don't understand why people are affraid of Flash ending in 2020. You can still stay on desktop with AIR and be successful with iOS and Android. People who are migrating on browsers are shooting themselves in the foot. The Browser is a bloody hell as environment.


19.12.2018, 11:49, "Carlos Rovira" <[email protected]>:
Hi Alex

El mar., 18 dic. 2018 a las 18:58, Alex Harui (<[email protected]>) escribió:

Two more ideas:

 

  1. Switch to Royale

We are already switching to Royale ;), but that is a long term process while encapsulate with AIR is something we can provide in few weeks and will let us control de change without any pressure from Browsers vendors about #flash2020
 
  2. Didn’t Flex use custom HTTP code used in the Flex installer?  Maybe it will get around this limit, but I think it had other limits like proxy handling.

Don't know anything about this. Is very interesting. Could you provide more info about what you refer and/or some links so I can check it?

thanks!

Carlos

 

 

-Alex

 

From: Carlos Rovira <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Tuesday, December 18, 2018 at 1:14 AM
To: "[email protected]" <[email protected]>
Subject: Re: Apache Flex AIR Application problems with a limitation of two HTTP request on windows

 

Many thanks for the suggestions Andrew!

We're doing some brainstorming and all those come very handy! :)

 

thanks! :)

 

El mar., 18 dic. 2018 a las 7:48, Frost, Andrew (<[email protected]>) escribió:

Hi

 

> We are using RemoteObject/AMF call so I think we don't have AFAIK to use Sockets :(

Ah okay .. do you have a choice of protocol when doing this? I’m not sure what the server side would support, but it looks like the “AMFChannel” class is defining protocol as “http”; if you could change that to “rtmp” then it would [I think] use a TCP socket rather than the Windows http functions..

 

My only other thought would be whether you could change the design of how the processing works so that it’s done more asynchronously i.e. one quick message from client to server to kick off the processing and then poll every second or so to see if it’s finished – but I’m not sure if that’s possible, I’ve not used remote objects or done the server side stuff…

 

Final option = a custom build of AIR, but that would be very expensive :-)

 

Good luck!

 

thanks

 

   Andrew

 

 

From: Carlos Rovira [mailto:[email protected]]
Sent: 17 December 2018 16:52
To: [email protected]
Subject: [EXTERNAL] Re: Apache Flex AIR Application problems with a limitation of two HTTP request on windows

 

Hi Andrew,

 

thanks for the suggestions:

 

El lun., 17 dic. 2018 a las 14:25, Frost, Andrew (<[email protected]>) escribió:

Hi Carlos

 

This looks like it’s to do with http 1.1 .. see the final recommendations in 8.1.4 of RFC 2616 [1]

 

But you can hopefully override it using the windows registry (see [2])

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

MaxConnectionsPerServer can be set to a value higher than 2. I guess you’d need an ANE to manipulate the registry though..

 

I'm was thinking as well in an ANE, but was hoping that someone knows some other direct way from AIR to do this, since creating an ANE just for this is a bit cumbersome.

 

 

I’m curious how you’re connecting .. is it via a URLLoader type object, rather than a Socket? I don’t think the same limitation would be there if you just used TCP/IP sockets so you could potentially get around things that way..?

 

We are using RemoteObject/AMF call so I think we don't have AFAIK to use Sockets :(

 

 

Thanks for the links!

 

Carlos

 

 

 

cheers

 

   Andrew

 

 

From: Carlos Rovira [mailto:[email protected]]
Sent: 17 December 2018 10:32
To: [email protected]
Subject: [EXTERNAL] Apache Flex AIR Application problems with a limitation of two HTTP request on windows

 

Hi,

 

we are in the process of encapsulate an existing Apache Flex app in Adobe AIR to overcome the #flash2020 problem with browsers.

 

In this transition, we found a problem with Adobe AIR in windows with a limit of two HTTP request to the same server. This seems due to Adobe AIR using WinlNet on Windows that has this 2 limit http request.

 

Seems we didn't saw this problem with Flex in browsers since those left behind this limit and allow this days 6 concurrent calls, but AIR, since used WinlNet, continues with the 2 concurrent call limit, that is a problem nowadays.

 

In the other hand don't find any reference to this problem on the internet, or some solution to apply in Adobe ARI, so maybe there's something I'm missing, since this problem should be found by many people trying to leverage existing Flex apps in AIR (or even creating others).

 

Must say this problem is seen with request that needs several time (due to some server processing) to complete and send a response.

 

If anyone know some way to overcome this will be of great help

 

Thanks in advance for your help

 

--

Carlos Rovira

 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 



--

Reply via email to