FluorineFX 是否足够成熟以用于大型 Web 应用程序？
我正处于开发一个用 Flex 编写的大型 Web 应用程序的规划阶段，想知道是否有人在大型生产环境中实际使用过 FluorineFX？
文档和在线社区使它看起来可能会在未来几年内被放弃，而且我还没有读到有关它在生产中使用的信息。
我也一直在评估 Weborb，但成本非常高，而且我对它的一般工作流程/设置并不完全满意。我还应该考虑其他解决方案吗？
I am in the planning stages of developing a large web application written in Flex and was wondering if anyone has actually used FluorineFX in a large production environment?
The documentation and online community makes it seem like it could be abandoned in the years to come and I have yet to read about it being used in production.
I have been assessing Weborb as well, but the costs are extremely high and I'm not entirely satisfied with the general workflow/setup of it. Are there any other solutions out there that I should consider?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我在一个带有 Flex 3 客户端的大型产品中使用 FlourineFx 取得了巨大成功，它实际上比它所取代的 ColdFusion (Adobe LiveCycle) 产品工作得更好。它确实需要一些配置才能正常工作，但一旦设置了配置文件，它似乎就可以很好地工作——话又说回来，它与 Adobe LiveCycle 所需的配置文件相同。
I've used FlourineFx with great success in a large product with a Flex 3 client, and it actually works better than the ColdFusion (Adobe LiveCycle) product it replaced. It does require some configuration to work correctly, but it seems to work quite well once your config files are set up -- then again, its the same config files that Adobe LiveCycle need.
不确定 FlourineFX。看起来要么才刚刚开始，要么就结束了。
使用 DotNet 和 Flex，我建议编写 Flex 客户端并使用 ASP.NET Web 服务进行通信。 Microsoft ASP.NET MVC 是一个出色的框架，免费且支持良好。请参阅：http://www.asp.net/mvc
使用 Web 服务的优点是客户端可以更改，因此，如果您将来决定不使用 Flex 或决定使用移动客户端，则服务将保持不变。另外，ASP.NET MVC 已经在一些非常大的网站上得到了验证，比如这里的 SO。
希望这有帮助。
Not sure about FlourineFX. It looks like it is either just getting started or ending.
Working with DotNet and Flex, I would recommend writing the Flex Client and using ASP.NET web services to communicate. Microsoft ASP.NET MVC is a wonderful framework that is free and well supported. See: http://www.asp.net/mvc
The advantage of using a web service is that the client can change so that if you decide against Flex in the future or decide to use a Mobile Client then the service will remain the same. Plus, ASP.NET MVC has been proven on some very large sites like SO here.
Hope this helps.