On Tue, 1 Jul 2008, Diez B. Roggisch wrote:
> Lukasz Szybalski schrieb:
>> "I still fail to see how this relates to reverse proxying? Might it be
>> that you don't know what that actually is?
>>
>> http://en.wikipedia.org/wiki/Reverse_proxy
>>
>> It has nothing to do with mod_proxy."
>>
>> Well,
>> I thought that the way you setup the tg app in production is by using
>> apache and mod_proxy, and pass all data back and fourth between apache
>> and tg cherry py service. You could use mod_proxy (which worked for
>> me) and mod_rewrite (which didn't work for me). From the link you
>> sent me: "The Apache HTTP Server may be extended with mod_proxy to be
>> used as a reverse proxy".
>
> Hm, the question is is what that actually means. For a reverse proxy
> being effective, it has to have caching or at least buffering
> capabilities. AFAIK there is at least no caching (without special other
> modules that is) in the apache available. So I know reverse proxying
> done using Squid or similar web-caches.
>
> Technically, mod_proxy does a very similar thing of course. But IMHO the
> term "reverse proxying" isn't justified there - it doesn't do any caching.
There is mod_disk_cache for Apache, fwiw.
-- Asheesh.
--
"I've seen, I SAY, I've seen better heads on a mug of beer"
-- Senator Claghorn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
