我几天前提出了这个问题（用 Java 开发视频聊天 Web 应用程序的最佳方法是什么？Flex 还是 JMF？）感谢那里给出的答案，我们决定使用 Flex 来实现它+ Red5，那么现在的问题是，我们如何将Red5实现到现有的Spring Web应用程序中？我们可以尽可能地利用 Spring 应用程序中当前的 Spring Security 配置，并能够调用其中的所有业务逻辑。所以我们想知道 Red5 是否必须部署在单独的服务器中，或者我们是否可以以某种方式将其作为单独的 servlet 部署在同一个 Spring 应用程序下，从而能够使用相同的 Spring Security 配置来保护 Red5 服务器？我们知道 Red5 配置是基于 Spring 的，因此我们认为我们可以将其与 Spring 一起部署为另一个 servlet...这可能吗？或者我们必须在另一台服务器上部署Red5并在其中配置另一个Spring安全实例？
I've made this question couple of days ago (What is the best approach to develop a video chat web application in Java? Flex or JMF?) thanks to the answers given there we've decided to implement it with Flex + Red5, so the question now is, how can we implement Red5 into the existing Spring Web application? We can take advantages as much as we can of the Spring Security configuration that is currently in the Spring application and be able to call all the bussiness logic in there. So we are wondering if Red5 has to be deployed in a separate server or if we can somehow deploy it under the same Spring application as a separate servlet thus being able to use the same Spring Security configuration to secure the Red5 server? We know that Red5 configuration is based on Spring and for that reason we suppose that we can deploy it as another servlet together with Spring... is it possible? or we have to deploy Red5 in another server and configure another Spring security instance inside it?
发布评论
评论（1）
很多问题 :)
基本上，您只需按照习惯编写服务器端逻辑，并使用您需要的所有应用程序上下文 xml，但请记住，您的主要入口点（至少来自 amf）将位于您的内部应用程序扩展类（任何额外的上下文都应该从那里加载）。
关于部署您的应用程序：
服务器-修改Tomcat-（我认为是最好的），
或者
服务器。
如果您选择第一个选项，您将能够以您一贯的方式设置您需要的一切，并且您还可以将它用作 servlet 容器，没有任何问题。
您可能会发现以下链接很有用：
应用程序
春季）
Lots of questions :)
Basically, you just keep writing your server side logic as you are used to, with all the application context xmls you need, but keep in mind, that your main entry point (at least from amf) will be inside your Application extension class (any extra contexts should be loaded from there).
About deploying your application:
server -modified Tomcat- (in my opinion is the best),
or
servers.
If you go with the first option, you'll be able to set up everything you need in a manner you always do, and you can also use it as a servlet container without any problems.
You might find the following links useful:
Applications
Spring)