全新开始，从 Flex 3 到 Catalyst
我们的 Flex 3 客户外联网应用程序的业务逻辑发生了太多变化，因此我已获得重新开始的许可......日期压力较小（我知道，你羡慕我......）。 相反，选择明显的 Flex 4 路径，Perl/Catalyst 似乎非常非常适合这个全新的场景，但我不想失去一些好处：
我们只有一组 .swf 模块，因此所有客户端都加载共享路径中的相同实际文件。
- 他们是虚拟主机。
- 每个域目录都有一个index.php。它加载带有密码的个性化文件以及加载共享.swf 的“真实”共享index.php。
- 没有跨域问题，因为 .swf 认为它位于真实域中，这要归功于 Apache 虚拟链接。
- .swf 中的所有个性化（业务数据和视觉首选项）都是从数据库中的首选项动态加载的。
似乎我可以使用 Catalyst 执行相同的操作，不是吗？甚至更容易，因为我可以让 Perl 应用程序“全局”响应不同虚拟主机中的相同参数，因此一切都可以在运行时决定
但 Flex 的巨大优势是我已经在客户端中加载了所有逻辑和首选项，所以服务器和数据传输的工作量真的非常低。唯一传输的数据是纯商业数据。没有首选项，没有页面，什么都没有。而且该应用程序始终知道客户是谁，因此查询非常非常干净。
所以这是我的两个问题：
Perl/Catalyst 中的持久性是管理类似事物的方法吗？
我到处阅读了很多关于未关闭的进程和线程的帖子，甚至是 cron 编程的服务器重新启动......作为“解决方案”，以及类似的性能问题。
- 我必须管理这些事情才能拥有稳定的服务器吗？
这听起来像是一颗定时炸弹，我们现在对我们的服务器感知性能感到非常非常自豪，只需很少的投资。
先感谢您
Things have changed way too much in the bussines logic for our Flex 3 customer extranet application, so I have received the permision to make a fresh start... with low date pressure (I know, you envy me...).
Instead choosing the obvious Flex 4 path, it seems that Perl/Catalyst fits very, very well in this brand new scenary, but I don´t want to lose some goodies:
We have just ONE set of .swf modules, so all clients load the same actual files in a shared path.
- They are Virtual Hosts.
- Each domain directory has a index.php. It loads a personalization file with passwords AND the "real" shared index.php that loads the shared .swf.
- No crossdomain problems because the .swf thinks that its in the true domain, thanks to the Apache virtual link.
- All personalization inside the .swf (bussines data and visual prefs) are loaded dinamically from preferences in a database
It seems that I can do the same with Catalyst, isn´t it? Even easier, because I can make the perl app to respond "globally" to the same arguments in different vhosts, so everything can be decide at runtime
But the great advantage of Flex is that I have all the logic and preferences already loaded in the client, so the work in the server and the data transference is really, really low. The only data that travels is pure bussines data. No preferences, no pages, no nothing. And the app always know WHO the client is, so the queries are really, really clean.
So here are my two questions:
Is the Persistence in Perl/Catalyst a way to manage something similar?
I have read a lot of posts, here and there, about unclosed processes and threads, even cron programmed restarting of the server... as a "solution", and similar performance problems.
- Must I manage such things to have a stable server?
It sounds ike a time bomb, and we are now very, very proud of our server perceived performance with a litle investment.
Thank you in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Catalyst 的好处是可以很容易地将 CPAN 中的各种好东西插入到您的应用程序中。您需要身份验证/授权、会话管理、数据库处理、PDF 生成、Excel 解析......？如果您能想到的话，CPAN 上的某个人可能已经完成并发布了它以供全世界使用。
我不太清楚你想要服务器做什么。如果它只是通过 JSON 或类似的东西向您的 SWF 应用程序提供数据，Perl Dancer (http://perldancer.org/) 可能也值得一看，它就像节食中的 Catalyst。 Catalyst 和 Dancer 都内置了 PSGI 支持，允许您以任何您喜欢的方式运行它。
我自己最近刚刚完成了卢森堡荷兰银行 其中我使用 Catalyst 作为 ExtJS 应用程序的后端解决方案。该应用程序在 FastCGI 下运行，非常健壮和稳定。我不知道你从哪里听说 Catalyst 进程存在漏洞，需要重新启动，但这只是无稽之谈。当然，如果您自己编写的程序出现泄漏，您可能会遇到问题，但框架本身非常稳定。另外，由于使用 Catalyst，我能够在很短的时间内开发出非常复杂的应用程序。我不知道如果没有 Catalyst，我如何能够做到这一点。
祝你项目顺利
抢
The nice thing about Catalyst is that it is very easy to plug all sorts of nice things from CPAN into your application. You need Authentication/Authorization, Session management, database handling, PDF generation, Excel parsing....? If you can think of it, someone on CPAN has probably done it already and published it for the world to use.
It is not exactly clear to me what you want the server to do. If it's just providing data to your SWF application through JSON or something similar, Perl Dancer (http://perldancer.org/) might also be interesting to look at, it's like Catalyst on a diet. Both Catalyst and Dancer have built in PSGI support allowing you to run it in any way you like.
Myself, I have just recently finished a project for ABN AMRO Bank Luxembourg in which I used Catalyst as the backend solution for an ExtJS application. The application is run under FastCGI and is extremely robust and stable. i don't know where you heard that Catalyst processes are leaky and need to be restarted, but that's just nonsense. Of course, if you program leaks yourself you might get yourself in problems, but the framework itself is very stable. Also, because of using Catalyst I was able to develop a very complex application is a very short time. I don't know how I could have managed it without Catalyst.
Good luck with you project
Rob