I actually chose to physically separate CFMX and flex...mostly because we'll have Flex apps that won't even touch the CFMX instances...plus for redundancy sake I don't want to have to take down � the available flex UI resources just to cycle a CFMX instance for whatever reason.
Here's our actual setup...
2 x 2CPU machine
JRun 4 with CFMX 6.1
Total of 3 Jrun instances running on each machine.
Two have CFMX, one has Flex.
Each CFMX instance belongs to a cluster. Cluster #1 consists of one instance on server A, on instance on server B. Same for Cluster #2
When the user access a Flex application it loads from the standalone 3rd JRun instance. The Flex app now pulls data from multiple applications running on either of those two CFMX clusters. In addition, there is a whole other WebLogic cluster it ties into for specific services.
I hope I'm not clouding things further!
Cheers,
Stace
_____
From: Dick Applebaum [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 30, 2004 2:21 PM
To: CF-Talk
Subject: Re: Flex is out
On Mar 30, 2004, at 11:13 AM, Stacy Young wrote:
> I can tell you from experience...RIA development for most typical j2ee
> development teams will be of a fraction of the cost vs traditional
> flash/remoting development. The difference in managing source code
> alone
> is worth big bucks to me...I've had my FLAs over-written a few too
> many
> times ;-)
>
> Stace
>
>
Now that seems to be a very valid justification.
Do you think that adding CFMX to that equation adds or detracts?
If CFMX is a plus, would CFMX & the taglibs, alone provide the
justification?
I don't know, and am assuming that there is a lot more to Flex than the
taglibs... that the taglibs provide rhe UI components and generate the
swf from XML.
TIA
Dick
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
