date:20170409

Re: Flex Air Support

2017-04-09 Thread lgabrielmf

  Oh, now that you’ve cleared up I could do some initial tests and it looks 
great. One can benefit a lot from using FlexJS to migrate the ActionScript 
application’s core to JS.

  I will definitely look at it later on.

  At this moment I don’t have the time to migrate the application. The first 
release of my product is planned for the next month. I love Apache Flex AIR, 
but I think it may be too risky to rely on Apache Air in the long run. As 
you’ve said there’s no guarantee that Adobe will continue it’s development. I 
still have some time, though. And I think all I can do for now is hope that 
Apache Flex live longer. It’s definitely a great technology and I had a lot of 
fun developing in it’s platform. 

  Cheers,

Gabriel



> On 9 Apr 2017, at 22:41, Nicholas Kwiatkowski-2 [via Apache Flex Development] 
>  wrote:
> 
> FlexJS is a framework that allows you to take your existing ActionScript 
> and build HTML5 based application from that. 
> 
> There is no support for the FlexSDK UI components -- but there are many 
> comparable components that exist and are being created.  Essentially, you 
> will be able to bring over your business logic, but you will need to 
> re-create your UI code from scratch to support the HTML5 environment. 
> 
> FlexJS is where a majority of this project's efforts are going at the 
> moment.  It will break us from the dependencies of the Flash and AIR 
> runtimes. 
> 
> On Sun, Apr 9, 2017 at 6:56 AM, lgabrielmf <[hidden email] 
> > wrote: 
> 
> >   Thanks a lot for the responses! 
> > 
> >   Let me ask another question then. What about the FlexJS project? Is it a 
> > safe alternative to migrate code from Flex Air/Actionscript to 
> > HTML/Javascript? 
> > 
> >   Cheers, 
> > 
> > Gabriel 
> > 
> > 
> > > On 3 Apr 2017, at 03:29, Alex Harui [via Apache Flex Development] < 
> > [hidden email] > 
> > wrote: 
> > > 
> > > 
> > > 
> > > On 4/2/17, 6:47 PM, "lgabrielmf" <[hidden email] 
> > > wrote: 
> > > 
> > > >Hello everyone! 
> > > > 
> > > >I'm finishing a product that I'll soon release to the market and I've 
> > used 
> > > >Apache Flex Air as the desktop client. How are the expectations about 
> > > >Apache 
> > > >Flex Air? Will it continue to be supported? 
> > > > 
> > > >Thanks for your attention. 
> > > 
> > > Hi, 
> > > 
> > > Apache Projects are volunteer-driven.  There is no corporation that can 
> > > affect it.  But that also means that it requires volunteers to keep it 
> > > running.  The best way to ensure the longevity of Apache Flex is to 
> > become 
> > > a committer and PMC member yourself, by offering patches for bug fixes, 
> > > tests and new features (and other non-coding contributions like 
> > > documentation).  As long as there are at least 3 PMC members who are 
> > > active in the project, it will go on "forever". 
> > > 
> > > -Alex 
> > > 
> > > 
> > > 
> > > If you reply to this email, your message will be added to the discussion 
> > below: 
> > > http://apache-flex-development.247.n4.nabble.com/Flex-Air-Support- 
> > > 
> > tp60972p60973.html  > . 
> > com/Flex-Air-Support-tp60972p60973.html> 
> > > To unsubscribe from Flex Air Support, click here  > > 
> > development.247.n4.nabble.com/template/NamlServlet.jtp? 
> > macro=unsubscribe_by_code=60972=bGdhYnJpZWxtZkBnbWFpbC5jb218Nj 
> > A5NzJ8NDk4NTA4MTUy>. 
> > > NAML  > > . 
> > com/template/NamlServlet.jtp?macro=macro_viewer=instant_ 
> > html%21nabble%3Aemail.naml=nabble.naml.namespaces. 
> > BasicNamespace-nabble.view.web.template.NabbleNamespace- 
> > nabble.view.web.template.NodeNamespace= 
> > notify_subscribers%21nabble%3Aemail.naml-instant_emails% 
> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
> > 
> > 
> > 
> > 
> > -- 
> > View this message in context: http://apache-flex- 
> > development.247.n4.nabble.com/Flex-Air-Support-tp60972p61060.html 
> > Sent from the Apache Flex Development mailing list archive at Nabble.com. 
> > 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-flex-development.247.n4.nabble.com/Flex-Air-Support-tp60972p61070.html
>  
> 
> To unsubscribe from Flex Air Support, click here 
> .
> NAML 
>

Re: Flex Air Support

2017-04-09 Thread Nicholas Kwiatkowski

FlexJS is a framework that allows you to take your existing ActionScript
and build HTML5 based application from that.

There is no support for the FlexSDK UI components -- but there are many
comparable components that exist and are being created.  Essentially, you
will be able to bring over your business logic, but you will need to
re-create your UI code from scratch to support the HTML5 environment.

FlexJS is where a majority of this project's efforts are going at the
moment.  It will break us from the dependencies of the Flash and AIR
runtimes.

On Sun, Apr 9, 2017 at 6:56 AM, lgabrielmf  wrote:

>   Thanks a lot for the responses!
>
>   Let me ask another question then. What about the FlexJS project? Is it a
> safe alternative to migrate code from Flex Air/Actionscript to
> HTML/Javascript?
>
>   Cheers,
>
> Gabriel
>
>
> > On 3 Apr 2017, at 03:29, Alex Harui [via Apache Flex Development] <
> ml-node+s247n60973...@n4.nabble.com> wrote:
> >
> >
> >
> > On 4/2/17, 6:47 PM, "lgabrielmf" <[hidden email]
> > wrote:
> >
> > >Hello everyone!
> > >
> > >I'm finishing a product that I'll soon release to the market and I've
> used
> > >Apache Flex Air as the desktop client. How are the expectations about
> > >Apache
> > >Flex Air? Will it continue to be supported?
> > >
> > >Thanks for your attention.
> >
> > Hi,
> >
> > Apache Projects are volunteer-driven.  There is no corporation that can
> > affect it.  But that also means that it requires volunteers to keep it
> > running.  The best way to ensure the longevity of Apache Flex is to
> become
> > a committer and PMC member yourself, by offering patches for bug fixes,
> > tests and new features (and other non-coding contributions like
> > documentation).  As long as there are at least 3 PMC members who are
> > active in the project, it will go on "forever".
> >
> > -Alex
> >
> >
> >
> > If you reply to this email, your message will be added to the discussion
> below:
> > http://apache-flex-development.247.n4.nabble.com/Flex-Air-Support-
> tp60972p60973.html  com/Flex-Air-Support-tp60972p60973.html>
> > To unsubscribe from Flex Air Support, click here  development.247.n4.nabble.com/template/NamlServlet.jtp?
> macro=unsubscribe_by_code=60972=bGdhYnJpZWxtZkBnbWFpbC5jb218Nj
> A5NzJ8NDk4NTA4MTUy>.
> > NAML  com/template/NamlServlet.jtp?macro=macro_viewer=instant_
> html%21nabble%3Aemail.naml=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/Flex-Air-Support-tp60972p61060.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS] feature/chart_work status

2017-04-09 Thread piotrz

Ahh I forgot to mention that you can see issue when you look into MDLExample.
Main TabBar do not display Tabs. 

Basically in TabBarView itemsCreated method has not been called.

If you lost in there I will put some basic example.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-feature-chart-work-status-tp61035p61069.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] feature/chart_work status

2017-04-09 Thread piotrz

Hi Peter,

After couple of hours of investigation I have found the reason and fixed
bug. You can check it. 
But still something is wrong in case when TabBar is using
TabsItemRendererFactoryForArrayData. If you could take a look that would be
great!

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-feature-chart-work-status-tp61035p61068.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] non-primitive static consts

2017-04-09 Thread Alex Harui

I just took a look at UIDUtil.

If I dump Core.SWC, the UIDUtil.js in there has the following:

goog.provide('org.apache.flex.utils.UIDUtil');
/* FlexJS Static Dependency List: org.apache.flex.utils.BinaryData*/

goog.require('org.apache.flex.utils.BinaryData');
goog.require('org.apache.flex.utils.Language');

Then, after -remove-circulars is used to build HelloWorldTLF the UIDUtils
in bin/js-debug has the following:

goog.provide('org.apache.flex.utils.UIDUtil');
/* FlexJS Static Dependency List: org.apache.flex.utils.BinaryData*/

goog.require('org.apache.flex.utils.BinaryData');

This should cause BinaryData to be loaded before UIDUtil.

Are you getting the same results?

Thanks,
-Alex

On 4/8/17, 10:04 PM, "Harbs"  wrote:

>
>> On Apr 9, 2017, at 12:50 AM, Alex Harui  wrote:
>> 
>> I assume this is only a problem for folks using -remove-circulars?
>> 
>I have not tested with remove-circulars truned off, so very possibly, yes.
>
>> I assume what is broken is the order of loaded files instead of
>>something
>> else?
>
>Correct. With the current status of remove-circulars, the only reliable
>way to deal with static values which are non-primitive are to use getters
>instead of static initializations.
>
>> Thanks,
>> -Alex
>> 
>> On 4/8/17, 9:46 PM, "Harbs"  wrote:
>> 
>>> Related issue:
>>> 
>>> The recent changes to Falcon has broken UIDUtil which has the
>>>following:
>>> private static const UIDBuffer:BinaryData = new BinaryData();
>>> 
>>> Unless something changes, this needs to be changed to a getter.
>>> 
 On Apr 8, 2017, at 11:40 PM, Harbs  wrote:

 Currently initializing non-primitive static types are a big no-no in
 FlexJS. It causes all kinds of javascript runtime errors due to
 non-defined types depending on the order of loaded files.

 I think this is an area which needs some improvement. The improvement
 can take two variations:

 1. We can simply disallow initializing non-primitive types at compile
 time, so at least there will be a compile-time warning of potential
 problems.
 2. We can somehow allow these initializations.

 I’m not sure if #2 is possible, but it would definitely be preferred
to
 #1 if it is.

 Thoughts?

 Harbs
>>> 
>> 
>

Re: [FlexJS] internal classes based on other classes

2017-04-09 Thread Alex Harui

For me, FactoryComposer.js in the TLF.swc has:

goog.provide('org.apache.flex.textLayout.compose.FactoryComposer');

goog.require('org.apache.flex.textLayout.compose.StandardFlowComposer');
goog.require('org.apache.flex.textLayout.compose.utils.FactoryHelper');
goog.require('org.apache.flex.textLayout.elements.BackgroundManager');
goog.require('org.apache.flex.textLayout.compose.IFactoryComposer');
goog.require('org.apache.flex.utils.Language');


Which looks right to me.  I'm wondering if your compiler is out of synch
with the flex-falcon repo.

-Alex

On 4/8/17, 10:05 PM, "Harbs"  wrote:

>
>> On Apr 9, 2017, at 12:46 AM, Alex Harui  wrote:
>> 
>> I'll look into it.  I thought I'd fixed that already.  I assume
>> BackgroundManager isn't one of the goog.requires in FactoryComposer.js?
>
>I don’t remember, and I already modified my state of TLF. If you need me
>to check, I can try and revert.
>
>> And I assume you cleaned out old JS files?
>
>Yes.
>
>> -Alex
>> 
>> On 4/8/17, 9:15 PM, "Harbs"  wrote:
>> 
>>> The current state of Falcon seems to be okay so far, but I just bumped
>>> into an interesting problem.
>>> 
>>> In TLF, there’s a class: FactoryComposer. FactoryComposer has an
>>>internal
>>> class called FactoryBackgroundManager which subclasses
>>> org.apache.flex.textLayout.elements.BackgroundManager.
>>> 
>>> Because FactoryBackgroundManager is an internal class, the normal
>>> dependency chain is not built and I’m getting an error on the following
>>> line:
>>> 
>>>goog.inherits(org.apache.flex.textLayout.compose.FactoryComposer.Factory
>>>Ba
>>> ckgroundManager,
>>>org.apache.flex.textLayout.elements.BackgroundManager);
>>> 
>>> This is because this code is running before  BackgroundManager is
>>>loaded.
>>> 
>>> The work-around is to move the internal class out into its own file,
>>>but
>>> I think this is something which should work.
>>> 
>>> Harbs
>> 
>

Re: git commit: [flex-asjs] [refs/heads/feature/chart-work] - Updates to MDL.

2017-04-09 Thread Peter Ent

I don't need to have DataProviderChangeNotifier do what I made it do. I
was thinking that using the same event was causing the problem in the MDL
tabs because that event causes all of the item renderers to be thrown
away. 

‹peter

On 4/9/17, 9:47 AM, "piotrz"  wrote:

>Peter,
>
>I just tested your changes. They are breaking the cases where I would like
>to change whole data provider once everything is renderer. I'm going to
>get
>back to the previous version and implement beads as I wrote above, late I
>will deeply look into the Tabs problems.
>
>Thanks,
>Piotr 
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FRe-git-commit-flex-asjs-refs-heads-f
>eature-chart-work-Updates-to-MDL-tp61043p61062.html=02%7C01%7C%7C67f6
>2c2e6d78473cc45c08d47f50565e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C
>636273430404170114=4eDrhNX%2BaPt0UDNbmmEybSlhOWqTLvOJKQeMZrERQhk%3D&
>reserved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread Harbs

I think Peter wrote the original implementation, and you are probably right on 
most of your points that a lot of the code should be pulled out into beads.

I’ll let Peter or Alex comment on the original implementation, but it could be 
it’s time to re-write some of it.

Harbs

> On Apr 9, 2017, at 10:14 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Therefore code to deal with authentication should not be in the base 
>> component.
> 
> So in that case should the code dealing with HTTPs headers should be removed?
> 
> I can see the class is also dealing with timeouts should that also be removed 
> and placed in a bead?
> 
> The class is also missing JS implementations of addBead, getBeadByType and 
> removeBead so it currently doesn’t support beads on the JS side. I assume we 
> will need to add JS implementations of those methods?
> 
> The method send deals with AIR only HTTP status events, that seems like it 
> should not be there at all? Why isn’t that a bead?
> 
> It only has SWF version of error handlers to deal with various AS errors 
> surely that also should also be a bead?
> 
> It seem to me we’re being rather inconsistent here.
> 
> Thanks,
> Justin

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread Justin Mclean

Hi,

> Therefore code to deal with authentication should not be in the base 
> component.

So in that case should the code dealing with HTTPs headers should be removed?

I can see the class is also dealing with timeouts should that also be removed 
and placed in a bead?

The class is also missing JS implementations of addBead, getBeadByType and 
removeBead so it currently doesn’t support beads on the JS side. I assume we 
will need to add JS implementations of those methods?

The method send deals with AIR only HTTP status events, that seems like it 
should not be there at all? Why isn’t that a bead?

It only has SWF version of error handlers to deal with various AS errors surely 
that also should also be a bead?

It seem to me we’re being rather inconsistent here.

Thanks,
Justin

Re: git commit: [flex-asjs] [refs/heads/feature/chart-work] - Updates to MDL.

2017-04-09 Thread piotrz

Peter,

I just tested your changes. They are breaking the cases where I would like
to change whole data provider once everything is renderer. I'm going to get
back to the previous version and implement beads as I wrote above, late I
will deeply look into the Tabs problems.

Thanks,
Piotr 



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-feature-chart-work-Updates-to-MDL-tp61043p61062.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread Harbs

On Apr 9, 2017, at 5:54 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> But still it would be great to have Bead which holds it. 
> 
> Can you elaborate why you think it should be in a bead?

Most use cases of HTTPService does not require authentication.

Therefore code to deal with authentication should not be in the base component.

Beads were designed with this exactly this in mind.

> This fixes a security issue on the JS side in an existing component. There no 
> PAYG cost AFAICS and it’s not adding a new feature or something that should 
> be optional.
> 
> If user authentication was broken in HTTPService on the AS side but worked in 
> JS would you think the best way to fix that was to add a bead?

Yes. If there is already code in there which deals with authentication, it 
should be removed and placed in a bead. Not everything in FlexJS is designed 
100% PAYG, but the cases where it’s not should be fixed and not compounded 
upon. It took me a while to get used to this style of coding as well, but I do 
think that we need the discipline to sticking with as much PAYG as we can.

Fully functional components SHOULD be composed in the Express components.

Thanks,
Harbs

Re: Flex Air Support

2017-04-09 Thread lgabrielmf

  Thanks a lot for the responses!

  Let me ask another question then. What about the FlexJS project? Is it a safe 
alternative to migrate code from Flex Air/Actionscript to HTML/Javascript? 

  Cheers,

Gabriel


> On 3 Apr 2017, at 03:29, Alex Harui [via Apache Flex Development] 
>  wrote:
> 
> 
> 
> On 4/2/17, 6:47 PM, "lgabrielmf" <[hidden email] 
> > wrote: 
> 
> >Hello everyone! 
> > 
> >I'm finishing a product that I'll soon release to the market and I've used 
> >Apache Flex Air as the desktop client. How are the expectations about 
> >Apache 
> >Flex Air? Will it continue to be supported? 
> > 
> >Thanks for your attention. 
> 
> Hi, 
> 
> Apache Projects are volunteer-driven.  There is no corporation that can 
> affect it.  But that also means that it requires volunteers to keep it 
> running.  The best way to ensure the longevity of Apache Flex is to become 
> a committer and PMC member yourself, by offering patches for bug fixes, 
> tests and new features (and other non-coding contributions like 
> documentation).  As long as there are at least 3 PMC members who are 
> active in the project, it will go on "forever". 
> 
> -Alex 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-flex-development.247.n4.nabble.com/Flex-Air-Support-tp60972p60973.html
>  
> 
> To unsubscribe from Flex Air Support, click here 
> .
> NAML 
> 




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Flex-Air-Support-tp60972p61060.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread piotrz

Understand now. If it not optional than probably can be as you stated as part
of API.

Sorry for misunderstanding.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-CORS-security-Allow-auth-credentials-to-be-passed-when-us-tp61050p61059.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread Justin Mclean

Hi,

> But still it would be great to have Bead which holds it. 

Can you elaborate why you think it should be in a bead?

This fixes a security issue on the JS side in an existing component. There no 
PAYG cost AFAICS and it’s not adding a new feature or something that should be 
optional.

If user authentication was broken in HTTPService on the AS side but worked in 
JS would you think the best way to fix that was to add a bead?

Thanks,
Justin

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread piotrz

Hi Justin,

But still it would be great to have Bead which holds it. Small separate
extension. Let user used to use bead and think in a FlexJS way not Flex.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-CORS-security-Allow-auth-credentials-to-be-passed-when-us-tp61050p61057.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

2017-04-09 Thread Justin Mclean

Hi,

HTTPService on the AS side supports this security feature via cross domain 
policies built into the Flash Player. CORS is a little more complex and 
sometimes requires both client and server configuration rather than just mostly 
server side as AS security does. I think users of FlexJS would want us to 
support security features for both JS and AS right? Currently JS security in 
HTTPService is IMO a little broken. 

It often said that security is not an optional feature at Apache. It seems you 
are asking me to make it an optional feature?

Anyway just so other people know what the change was. I added this JS only 
method to HTTPService:
COMPILE::JS
public function set withCredentials(value:Boolean):void {
var element:XMLHttpRequest = this.element as XMLHttpRequest;
element.withCredentials = value;
}
This line of code is required to support a common scenario i.e. calling a API 
on a different server from the domain the original page was served from. It’s 
JS only and has zero performance or size impact on the AS side so as far as I 
can see there no PAYG implications. Not having it may force a user to disable 
security to get their application to work. If is not set then cookies and/or 
user credentials are not passed on with requests which stop most forms of user 
authentication from working.

I did consider turning it on by default for all requests and adding that one 
line of code to the send method but they may be some cases where users do not 
want it.

Thanks,
Justin

Re: Flex Air Support

Re: Flex Air Support

Re: [FlexJS] feature/chart_work status

Re: [FlexJS] feature/chart_work status

Re: [FlexJS] non-primitive static consts

Re: [FlexJS] internal classes based on other classes

Re: git commit: [flex-asjs] [refs/heads/feature/chart-work] - Updates to MDL.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: git commit: [flex-asjs] [refs/heads/feature/chart-work] - Updates to MDL.

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: Flex Air Support

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

Re: git commit: [flex-asjs] [refs/heads/develop] - CORS security. Allow auth credentials to be passed when using cross site calls. This is required as well as setting the Access-Control-Allow-Origin h

16 matches

Site Navigation

Mail list logo

Footer information