[mod_python] Swig, and mod_ssl

That'd be interesting to see. 

I'd really appreciate a lamens terms explanation of what it is you're
trying to get out of mod_ssl and what are the steps issues involved with
it? I'm somewhat mod_ssl ingorant - I've used it to set up SSL sites and
I'm somwhat familiar with use of openssl to generate certificates and
such, but I know next to nothing about mod_ssl internals.

P.S. Does SWIG really have to be involved in order for this to work?

--
  Gregory (Grisha) Trubetskoy
       grisha at modpython.org

On Thu, 17 Aug 2000, Rich Salz wrote:

> Back in mid-July, I wrote rsalz at caveosystems.com wrote:
> > Swig (http://www.swig.org) is a "compiler" that can parse most C
> > header files and automatically generate code for Perl, Tcl, Python,
> > and Java.  At a rough guess, approximately half of mod_python.c could
> > be replaced by a couple-dozen lines.  I wonder if it makes sense
> > to use SWIG, and for sites without it, include the Swig output.
> > (Just like some programs include the output of Yacc, for those without it.)
> > 
> > Second question, which motivated the first: anyone looked at what
> > could/should be added to the mod_python objects when mod_ssl is used?
> 
> Here is what I am going to end up doing.  I added a "get_swig_handle"
> method that returns the request_rec code into the SWIG representation
> of a pointer.  I'll then write little SWIG code to pull things out of
> the mod_ssl context.  I'll send get_swig_handle and a sample use if
> there's interest.
> 	/r$
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python
>