BlazeDS ChanelSet login convert to Royale

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

BlazeDS ChanelSet login convert to Royale

radu
Hello, 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
				xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
	<fx:Script>
		<![CDATA[
			import mx.messaging.ChannelSet;
			import mx.messaging.channels.AMFChannel;
			import mx.messaging.channels.StreamingAMFChannel;
			import mx.messaging.messages.CommandMessage;
			import mx.rpc.AsyncResponder;
			import mx.rpc.AsyncToken;
			import mx.rpc.events.FaultEvent;
			import mx.rpc.events.ResultEvent;
			public var cs:ChannelSet=null;
			private var amfChannel:AMFChannel;
			public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"

			public function main():void
			{
				cs = new ChannelSet();
				amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
				cs.addChannel(amfChannel);	
			}
			
			public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
			{
				but.label = "checkAPIVersion Success";
			}
			
			private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
			{
				but.label = "Fault";
			}

			protected function login(event:MouseEvent=null):void
			{
				var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
				token.addResponder(	new AsyncResponder(checkAPIVersion, handleLoginFault));
			}
			
		

		]]>
	</fx:Script>
	<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

Thank you,
Radu 
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Carlos Rovira-2
Hi Radu,

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

I recomend you to create a try the following test app :

Java part:

Royale client:

and check this:

things like turn enable-small-messages to false are very important to have success

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

thanks


El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:
Hello, 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
				xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
	<fx:Script>
		<![CDATA[
			import mx.messaging.ChannelSet;
			import mx.messaging.channels.AMFChannel;
			import mx.messaging.channels.StreamingAMFChannel;
			import mx.messaging.messages.CommandMessage;
			import mx.rpc.AsyncResponder;
			import mx.rpc.AsyncToken;
			import mx.rpc.events.FaultEvent;
			import mx.rpc.events.ResultEvent;
			public var cs:ChannelSet=null;
			private var amfChannel:AMFChannel;
			public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"

			public function main():void
			{
				cs = new ChannelSet();
				amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
				cs.addChannel(amfChannel);	
			}
			
			public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
			{
				but.label = "checkAPIVersion Success";
			}
			
			private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
			{
				but.label = "Fault";
			}

			protected function login(event:MouseEvent=null):void
			{
				var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
				token.addResponder(	new AsyncResponder(checkAPIVersion, handleLoginFault));
			}
			
		

		]]>
	</fx:Script>
	<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

Thank you,
Radu 


--
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

radu
Hi Carlos,
   
  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.
  Hope you can share a sample of the finished product.

Thank you,
Radu

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:
Hi Radu,

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

I recomend you to create a try the following test app :

Java part:

Royale client:

and check this:

things like turn enable-small-messages to false are very important to have success

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

thanks


El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:
Hello, 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
				xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
	<fx:Script>
		<![CDATA[
			import mx.messaging.ChannelSet;
			import mx.messaging.channels.AMFChannel;
			import mx.messaging.channels.StreamingAMFChannel;
			import mx.messaging.messages.CommandMessage;
			import mx.rpc.AsyncResponder;
			import mx.rpc.AsyncToken;
			import mx.rpc.events.FaultEvent;
			import mx.rpc.events.ResultEvent;
			public var cs:ChannelSet=null;
			private var amfChannel:AMFChannel;
			public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"

			public function main():void
			{
				cs = new ChannelSet();
				amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
				cs.addChannel(amfChannel);	
			}
			
			public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
			{
				but.label = "checkAPIVersion Success";
			}
			
			private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
			{
				but.label = "Fault";
			}

			protected function login(event:MouseEvent=null):void
			{
				var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
				token.addResponder(	new AsyncResponder(checkAPIVersion, handleLoginFault));
			}
			
		

		]]>
	</fx:Script>
	<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

Thank you,
Radu 


--
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Carlos Rovira-2
Hi Radu,

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:
Hi Carlos,
   
  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.
  Hope you can share a sample of the finished product.

Thank you,
Radu

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:
Hi Radu,

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

I recomend you to create a try the following test app :

Java part:

Royale client:

and check this:

things like turn enable-small-messages to false are very important to have success

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.
As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

thanks


El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:
Hello, 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
				xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
	<fx:Script>
		<![CDATA[
			import mx.messaging.ChannelSet;
			import mx.messaging.channels.AMFChannel;
			import mx.messaging.channels.StreamingAMFChannel;
			import mx.messaging.messages.CommandMessage;
			import mx.rpc.AsyncResponder;
			import mx.rpc.AsyncToken;
			import mx.rpc.events.FaultEvent;
			import mx.rpc.events.ResultEvent;
			public var cs:ChannelSet=null;
			private var amfChannel:AMFChannel;
			public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"

			public function main():void
			{
				cs = new ChannelSet();
				amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
				cs.addChannel(amfChannel);	
			}
			
			public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
			{
				but.label = "checkAPIVersion Success";
			}
			
			private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
			{
				but.label = "Fault";
			}

			protected function login(event:MouseEvent=null):void
			{
				var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
				token.addResponder(	new AsyncResponder(checkAPIVersion, handleLoginFault));
			}
			
		

		]]>
	</fx:Script>
	<mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

Thank you,
Radu 


--


--
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Alex Harui-2

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 

Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Greg Dove

Hi Alex,

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )



On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 

Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Alex Harui-2

IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.

 

My 2 cents,

-Alex

 

From: Greg Dove <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 


Hi Alex,

 

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

 

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )

 

 

 

On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 

Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Greg Dove
AC = mx ArrayCollection
AL = royale ArrayList

The custom stuff is to send *both* AC and AL as AC (which the server side was always expecting), but always receive AC as AL. 

I think it was always receiving AC as plain Array in the past, so if this is acceptable for now, then I could do what you suggest. 
If yes, I will look at that towards end of my day today - if it needs a bit of tweaking then it might not be until tomorrow that I get it in.
The other main change is in AMFNetConnection to support concurrent requests - this still needs further updates to support 'batching' calls into a single request (but that is less of an issue than the fix for concurrent requests, because subsequent requests were cancelling earlier ones that were not yet complete).






On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <[hidden email]> wrote:

IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.

 

My 2 cents,

-Alex

 

From: Greg Dove <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 


Hi Alex,

 

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

 

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )

 

 

 

On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 

Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Carlos Rovira-2
Hi Greg,

for me is ok to commit in the actual state, and form that point continue fixing things in Apache Royale.
But is up to you to manage this.

thanks



El jue., 17 ene. 2019 a las 20:38, Greg Dove (<[hidden email]>) escribió:
AC = mx ArrayCollection
AL = royale ArrayList

The custom stuff is to send *both* AC and AL as AC (which the server side was always expecting), but always receive AC as AL. 

I think it was always receiving AC as plain Array in the past, so if this is acceptable for now, then I could do what you suggest. 
If yes, I will look at that towards end of my day today - if it needs a bit of tweaking then it might not be until tomorrow that I get it in.
The other main change is in AMFNetConnection to support concurrent requests - this still needs further updates to support 'batching' calls into a single request (but that is less of an issue than the fix for concurrent requests, because subsequent requests were cancelling earlier ones that were not yet complete).






On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <[hidden email]> wrote:

IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.

 

My 2 cents,

-Alex

 

From: Greg Dove <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 


Hi Alex,

 

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

 

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )

 

 

 

On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 



--
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Greg Dove

fyi I will aim to get something in tomorrow. I'm short of time today with family commitments tonight.
-Greg




On Fri, Jan 18, 2019 at 9:02 AM Carlos Rovira <[hidden email]> wrote:
Hi Greg,

for me is ok to commit in the actual state, and form that point continue fixing things in Apache Royale.
But is up to you to manage this.

thanks



El jue., 17 ene. 2019 a las 20:38, Greg Dove (<[hidden email]>) escribió:
AC = mx ArrayCollection
AL = royale ArrayList

The custom stuff is to send *both* AC and AL as AC (which the server side was always expecting), but always receive AC as AL. 

I think it was always receiving AC as plain Array in the past, so if this is acceptable for now, then I could do what you suggest. 
If yes, I will look at that towards end of my day today - if it needs a bit of tweaking then it might not be until tomorrow that I get it in.
The other main change is in AMFNetConnection to support concurrent requests - this still needs further updates to support 'batching' calls into a single request (but that is less of an issue than the fix for concurrent requests, because subsequent requests were cancelling earlier ones that were not yet complete).






On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <[hidden email]> wrote:

IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.

 

My 2 cents,

-Alex

 

From: Greg Dove <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 


Hi Alex,

 

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

 

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )

 

 

 

On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 



--
Reply | Threaded
Open this post in threaded view
|

Re: BlazeDS ChanelSet login convert to Royale

Greg Dove
I pushed updates a short while ago. Note the caveats I mentioned earlier about ArrayCollection and ArrayList.

Please let me know any feedback or issues.
cheers
Greg


On Fri, Jan 18, 2019 at 5:56 PM Greg Dove <[hidden email]> wrote:

fyi I will aim to get something in tomorrow. I'm short of time today with family commitments tonight.
-Greg




On Fri, Jan 18, 2019 at 9:02 AM Carlos Rovira <[hidden email]> wrote:
Hi Greg,

for me is ok to commit in the actual state, and form that point continue fixing things in Apache Royale.
But is up to you to manage this.

thanks



El jue., 17 ene. 2019 a las 20:38, Greg Dove (<[hidden email]>) escribió:
AC = mx ArrayCollection
AL = royale ArrayList

The custom stuff is to send *both* AC and AL as AC (which the server side was always expecting), but always receive AC as AL. 

I think it was always receiving AC as plain Array in the past, so if this is acceptable for now, then I could do what you suggest. 
If yes, I will look at that towards end of my day today - if it needs a bit of tweaking then it might not be until tomorrow that I get it in.
The other main change is in AMFNetConnection to support concurrent requests - this still needs further updates to support 'batching' calls into a single request (but that is less of an issue than the fix for concurrent requests, because subsequent requests were cancelling earlier ones that were not yet complete).






On Fri, Jan 18, 2019 at 8:23 AM Alex Harui <[hidden email]> wrote:

IMO, if it isn’t going to break anything and will allow this potential user to test something, check in what you have and make it general later.

 

My 2 cents,

-Alex

 

From: Greg Dove <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 11:06 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 


Hi Alex,

 

I can answer that. It's not customer approval. The changes are for AMFBinaryData mainly. But I put in a bunch of custom stuff - which represent an incomplete and custom IExternalizable support that only targets ArrayCollection/ArrayList for now.

 

I need to remove that, and re-implement as a general solution (preferably retaining some opt-in/PAYG support for the 'custom' approach we are using which is good for transition management between legacy code and royale-specific work )

 

 

 

On Fri, Jan 18, 2019 at 7:53 AM Alex Harui <[hidden email]> wrote:

Carlos,  why do you need your customer’s approval to commit fixes for RemoteObject?  The sooner you can commit those changes, the better it will be for the community, IMO.

 

-Alex

 

From: Carlos Rovira <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, January 17, 2019 at 7:48 AM
To: "[hidden email]" <[hidden email]>
Subject: Re: BlazeDS ChanelSet login convert to Royale

 

Hi Radu,

 

we'll do at some time, but that would be when our client want to show it into public, so this could be not soon...As he give us green flag, hope to share it since I think it's becoming very cool Apache Royale App :)

 

El jue., 17 ene. 2019 a las 16:17, radu birsan (<[hidden email]>) escribió:

Hi Carlos,

   

  Thank you for your effort.  Having a complex AMF application ported to Royal would encourage us to start porting our app.

  Hope you can share a sample of the finished product.

 

Thank you,

Radu

 

On Thu, Jan 17, 2019 at 4:51 PM Carlos Rovira <[hidden email]> wrote:

Hi Radu,

 

this is actually working in Royale. Being said that We (Greg and I) have some fixes for RemoteObject that still didn't put on Apache Royale. Will upload soon as we end our migration (hopefully 1-2 weeks from now). But you can start trying a simple example.

 

I recomend you to create a try the following test app :

 

Java part:

 

Royale client:

 

and check this:

 

things like turn enable-small-messages to false are very important to have success

 

Just let you know that we are migrating a flex application using Jewel and MX RemoteObject and we are receiving/sending very complex graphs with AMF successfully.

As we get some free time (hopefully 2-3 weeks from now), Greg had in mind to complete RemoteObject implementation with enable-small-messages support too.

 

thanks

 

 

El jue., 17 ene. 2019 a las 13:08, radu birsan (<[hidden email]>) escribió:

Hello, 

 

   I have a simple flex login module that uses mx:ChannelSet. Any idea on how to make this work with Roylale js. 

 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
                          xmlns:mx="library://ns.adobe.com/flex/mx"  creationComplete="main()">
    <fx:Script>
           <![CDATA[
                   import mx.messaging.ChannelSet;
                   import mx.messaging.channels.AMFChannel;
                   import mx.messaging.channels.StreamingAMFChannel;
                   import mx.messaging.messages.CommandMessage;
                   import mx.rpc.AsyncResponder;
                   import mx.rpc.AsyncToken;
                   import mx.rpc.events.FaultEvent;
                   import mx.rpc.events.ResultEvent;
                   public var cs:ChannelSet=null;
                   private var amfChannel:AMFChannel;
                   public var serverSTUB:String = "http://voip-manager.spherecom.com:9080"
 
                   public function main():void
                   {
                          cs = new ChannelSet();
                          amfChannel = new AMFChannel("my-longpolling-amf",serverSTUB + "/RiaService" + "/messagebroker/amflongpolling");
                          cs.addChannel(amfChannel);     
                   }
                   
                   public function checkAPIVersion(event:ResultEvent = null, token:Object = null):void
                   {
                          but.label = "checkAPIVersion Success";
                   }
                   
                   private function handleLoginFault(event:FaultEvent = null, token:Object = null):void
                   {
                          but.label = "Fault";
                   }
 
                   protected function login(event:MouseEvent=null):void
                   {
                          var token:AsyncToken = cs.login('rbirsan'.toUpperCase(), "ThisISWork?");
                          token.addResponder(    new AsyncResponder(checkAPIVersion, handleLoginFault));
                   }
                   
           
 
           ]]>
    </fx:Script>
    <mx:Button label="Login!" id="but" width="200" click="login(event)" />
</mx:Application>

 

Thank you,

Radu 


 

--

Carlos Rovira

 


 

--

Carlos Rovira

 



--