Hello,
Trying to figure out if Royale can log in to a existing BlazeDS server.
Can somebody confirm the login works with Royale?
I uploaded the project on git:
https://github.com/radubirsan/MXBlazeDS
Thank you,
Rady
On Tue, Dec 18, 2018 at 8:48 AM Frost, Andrew
wrote:
> Hi
>
>
Hi,
thanks for the suggestions, our problem is that server process is very
complex and calls lots of external services. All of that requires time.
It's clear that we need a refactor in server side.
I''ll be posting this on flex user list as Piotr says
thanks all for the support! :)
Carlos
El
Hi Carlos,
just for the case if you end up to queue your requests:
There's a "PureMVC AsyncCommand utility" available which does something like
this [1]:
"The AsyncCommand utility offers a solution to the problem of executing a
series of commands each of which may need to complete one or more
Carlos,
Maybe try post problem on Flex users list.
Piotr
On Thu, Dec 20, 2018, 12:49 PM Carlos Rovira
wrote:
> Hi Olaf,
>
> yes the problem is doing http request to same server, we tried to some
> changes with subdomains and that works, but doesn't seem the best solution,
> but somewhat
Hi Olaf,
yes the problem is doing http request to same server, we tried to some
changes with subdomains and that works, but doesn't seem the best solution,
but somewhat "hacking" ;)
we're investigating some paths to solve this. Since this affects our
RemoteObject operations, our focus is in
Hi Carlos,
interesting topic, good to know about it!
If I understand it correctly, the connection limit is related to the same
domain name.
Maybe one solution could be to outsource heavy server-side requests to
another server/domain?
If that doesn't work, is it not just a possibility to queue
Many thanks Piotr,
I'll check that class, it could be of help to fix this issue for now.
Carlos
El mié., 19 dic. 2018 a las 12:10, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Carlos,
>
> I think Alex is referring to that one [1].
>
> [1]
>
Hi Carlos,
I think Alex is referring to that one [1].
[1]
https://github.com/apache/flex-utilities/blob/develop/flex-installer/installer/src/org/apache/flex/packageflexsdk/util/ApacheURLLoader.as
Thanks, Piotr
śr., 19 gru 2018 o 11:55 Ramazan Ergüder Bekrek
napisał(a):
> I don't understand
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"
Hi Alex
El mar., 18 dic. 2018 a las 18:58, Alex Harui () 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
Two more ideas:
1. Switch to Royale
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.
-Alex
From: Carlos Rovira
Reply-To: "users@royale.apache.org"
Date: Tuesday, December 18, 2018
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 ()
escribió:
> Hi
>
>
>
> > We are using RemoteObject/AMF call so I think we don't have AFAIK to
> use Sockets :(
>
> Ah okay .. do
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
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
14 matches
Mail list logo
