Hi
The AJP adatpor is a server adatpor dedicated to connecting Seaside to Apache. You can't use it without Apache because it doesn't understand HTTP. Instead it uses the binary AJPv13 protocol which is more efficient and simpler to parse. The result is a lightweight adatpor without any external dependencies but Grease/Seaside. In the multipart parser special attention has been paid to avoid unnecessary copy operations. Streaming however is currently not supported. I've been using this adaptor for development over the last several months and have been able to get very good performance and reliability. If you want to do your own benchmarking there are some static request handlers in AJP-Tests-Core. They avoid sessions/continuations/backtracking, you want to benchmark the adatpor, not Seaside. One thing to note is that I recommend turning keep-alive on, it makes a performance difference. The setup is described in the Seaside book [1], it's the same as setting up HTTP proxying but the protocol is ajp instead of http. I should note that there's a similar project for Comanche [2]. [1] http://book.seaside.st/book/advanced/deployment/deployment-apache/mod-proxy-ajp [2] http://www.squeaksource.com/KomAjpServer Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hurray! Excellent news, Philippe. Glad to see it finally "released". :)
Julian On Thu, Dec 2, 2010 at 7:00 AM, Philippe Marschall <[hidden email]> wrote: > Hi > > The AJP adatpor is a server adatpor dedicated to connecting Seaside to > Apache. You can't use it without Apache because it doesn't understand > HTTP. Instead it uses the binary AJPv13 protocol which is more > efficient and simpler to parse. The result is a lightweight adatpor > without any external dependencies but Grease/Seaside. In the multipart > parser special attention has been paid to avoid unnecessary copy > operations. Streaming however is currently not supported. > > I've been using this adaptor for development over the last several > months and have been able to get very good performance and > reliability. If you want to do your own benchmarking there are some > static request handlers in AJP-Tests-Core. They avoid > sessions/continuations/backtracking, you want to benchmark the > adatpor, not Seaside. One thing to note is that I recommend turning > keep-alive on, it makes a performance difference. > > The setup is described in the Seaside book [1], it's the same as > setting up HTTP proxying but the protocol is ajp instead of http. I > should note that there's a similar project for Comanche [2]. > > [1] http://book.seaside.st/book/advanced/deployment/deployment-apache/mod-proxy-ajp > [2] http://www.squeaksource.com/KomAjpServer > > Cheers > Philippe > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Yes, this is really cool and important to have this kind of
"enterprise" support. Now what about mod_cluster? How do I use that one? :-) Lukas On 2 December 2010 17:47, Julian Fitzell <[hidden email]> wrote: > Hurray! Excellent news, Philippe. Glad to see it finally "released". :) > > Julian > > On Thu, Dec 2, 2010 at 7:00 AM, Philippe Marschall > <[hidden email]> wrote: >> Hi >> >> The AJP adatpor is a server adatpor dedicated to connecting Seaside to >> Apache. You can't use it without Apache because it doesn't understand >> HTTP. Instead it uses the binary AJPv13 protocol which is more >> efficient and simpler to parse. The result is a lightweight adatpor >> without any external dependencies but Grease/Seaside. In the multipart >> parser special attention has been paid to avoid unnecessary copy >> operations. Streaming however is currently not supported. >> >> I've been using this adaptor for development over the last several >> months and have been able to get very good performance and >> reliability. If you want to do your own benchmarking there are some >> static request handlers in AJP-Tests-Core. They avoid >> sessions/continuations/backtracking, you want to benchmark the >> adatpor, not Seaside. One thing to note is that I recommend turning >> keep-alive on, it makes a performance difference. >> >> The setup is described in the Seaside book [1], it's the same as >> setting up HTTP proxying but the protocol is ajp instead of http. I >> should note that there's a similar project for Comanche [2]. >> >> [1] http://book.seaside.st/book/advanced/deployment/deployment-apache/mod-proxy-ajp >> [2] http://www.squeaksource.com/KomAjpServer >> >> Cheers >> Philippe >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2010/12/3 Lukas Renggli <[hidden email]>:
> Yes, this is really cool and important to have this kind of > "enterprise" support. > > Now what about mod_cluster? How do I use that one? :-) http://article.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside/22629 This was currently more rough edges so I sent the mail only to the developers list. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |