[OGo-Users] OGo + Apache2 instructions

[Helge Hess]

On Dienstag, 15. Juli 2003, at 8:32 Uhr, Henrik Holmboe wrote:
>  No, the current mod_ngbjweb is only usable with Apache 1.3.

Fortunatly this is resolved now :-)

>  As stated
>  Im using mod_proxy instead. I remember reading on an ml posting that
>  this was possible. I do not know the impact of not using mod_ngbjweb
>  or the difference with these two solutions. So far I havent seen any
>  odd behaviour (besides that OGo is terminating, but that is a know
>  issue).
>
>  Maybe someone that knows more about this might shed some light on
>  possible drawbacks to using mod_proxy instead of mod_ngbjweb?

I think I qualify ;-)

The differences between mod_proxy and mod_ngobjweb are basically two:
a) streaming proxy vs non-streaming proxy
b) snsd support

Mod_proxy is a streaming proxy which passes on content to SOPE as soon 
as something is received. Mod_ngobjweb read the full request before 
passing it one to SOPE.
This is good, because SOPE is not (thanks god) multithreaded and 
therefore is blocked as long mod_proxy streams a request in (especially 
bad on slow connections). Also if a user does a large upload and 
cancels it, only Apache need to deal with it (with mod_ngobjweb in 
front, SOPE only needs to deal with complete, well received requests) 
;-)

And of course snsd support, the load balancer, currently only available 
with SKYRIX distributions.

best regards,
   Helge
-- 
OpenGroupware.org	http://www.opengroupware.org/