Re: [Erlyaws-list] mod_python for yaws ??

[ke h. <ke...@re...>]

On Aug 31, 2006, at 4:32 AM, Bob Ippolito wrote:

> On 8/30/06, ke han <ke...@re...> wrote:
>> Does anyone know how mod_python for apache works?  If its not too
>> hard, I would like to make something like this for yaws...or at least
>> a special purpose interface for running trac through yaws.
>> My impetus for this is to use trac (trac.edgewall.com) served by  
>> yaws.
>> Currently supported methods for serving trac pages are: cgi,
>> fast_cgi, mod_python and tracd (trac's standalone http server).
>>
>> If its possible, I will integrate yaws to trac by starting with the
>> howto for running python as a port:
>> http://wiki.trapexit.org/index.php/
>> Writing_an_Erlang_Port_using_OTP_Principles
>>
>> The trouble is, I have no clue what mod_python for apache does.  What
>> info and structure from the http request am I supposed to pass on to
>> the python process?
>
> You definitely don't want to try and emulate mod_python. fastcgi or
> reverse proxy to tracd would be significantly easier and more
> flexible.

ok, so any pointers on where to start with fast_cgi or reverse proxy  
to tracd?
I know that the point of fast_cgi is to keep the python process  
running between calls.  Seems like I can use the howto referenced  
above for this. ;-)   But what do I actually pass from the http  
request into python?  I gues this is like saying what is the fast_cgi  
protocol...but thats basically where I am.
Doing reverse proxy to tracd sounds straightforward but less  
desirable in terms of performance and solution reuse for other types  
of apps and for my purposes I need the requests coming through as  
https.  I've read quite a few problems exist when trying to proxy  
into tracd with an https front end.

thanks for saving me some time on the mod_python attack...
Any more takers on my next steps?
ke han

>
> -bob