浏览 6357 次
该帖已经被评为新手帖
|
|
---|---|
作者 | 正文 |
发表时间:2006-11-16
唉,帖子内容太大,只能上传附件了! <server port="8005"></server> 声明:ITeye文章版权属于作者,受法律保护。没有作者书面许可不得转载。
推荐链接
|
|
返回顶楼 | |
发表时间:2006-11-16
本来是想copy 剩下的部分的,但已经上传附件了,也就不用copy了,可我确找不到怎么删除自己的回复的方法。哈哈
<server port="8005"></server> |
|
返回顶楼 | |
发表时间:2006-11-19
这个帖子中用得是mod_jk,连接Tomcat。可是我从javaeye上看到有人说这种方式已经落伍了,用了一种modajp得东东,小弟google了一下,没有具体得解释。谁能给小弟讲讲!
|
|
返回顶楼 | |
发表时间:2006-11-19
呵呵,可能提到modajp得那位仁兄打错了,应该是mod_proxy_ajp吧,刚看到一篇blog
mod_jk is dead. Long live mod_proxy_ajp It appears that there is *yet another* change coming to the recommended way to connect Tomcat to Apache. I've tried mod_proxy, mod_webapp, mod_jk and mod_jk2 - well it appears that the new direction is mod_proxy_ajp. mod_proxy allows Apache to proxy requests to other systems. Before Apache 2.2 it would only work with FTP and HTTP, but now it handles AJP too. So before Apache 2.2 you could rule out mod_webapp (easy to configure, but obsolete) and mod_jk2 (fallen behind mod_jk v1!) and your choice was mod_proxy (easy to get working but easy to create a security hole) or mod_jk (harder to configure but generally better). If you can avoid the security hazards, it looks like mod_proxy_ajp may soon be a better option from Apache 2.2 and on. Either that or it’s just going to be another way to confuse everyone. The next change I expect is that someone equipped with GCJ is going to come up with mod_tomcat - just compile the whole thing as an Apache module and forget all this connector nonsense! |
|
返回顶楼 | |
发表时间:2006-11-20
看来这个贴子要沉到底了,我本来想希望各位大侠看了我发的附件之后,发表一下自己的看法,看做负载均衡还有没有更好的方式,但却没人理,估计是...
|
|
返回顶楼 | |
发表时间:2006-11-20
我都已经写过很详细的,自己去搜索
|
|
返回顶楼 | |