Hi all,

currently I’m using Apache Flex BlazeDS as backend for my Royale applications.

This has somewhat become a little old and I do need to do quite some tweaking 
to get it working with Royale and especially with new Spring, Spring-Boot and 
Spring-Security.
So I guess doing some update of that and re-releasing does sound like a good 
idea.

But I think it would be better to do a clean cut and optimize it for usage with 
Royale.

I’d even like to call it something “RoyaleDS” to make the link Rolyale + 
RoyaleDS a little more obvious than the old Flex + BlazeDS pair.

What do you think?

Right now the Flex project seems like we’re keeping the lights on in an empty 
building and I doubt things will improve soon. Starting to move the things we 
want to keep on maintaining to Royale sounds like a good thing to to.
Perhaps even a stripped down version of the mavenizer.

Chris

Reply via email to