[Windmill-dev] https; file uploads; extjs and click support

Mikeal Rogers mikeal at osafoundation.org
Mon Dec 17 00:45:04 PST 2007


>>
> No, sorry for being unclear.  I meant Twisted.  The Twisted server  
> that Zope can hook up to is their NG server, which is WSGI.

Oh yes, twisted does have a WSGI server, i've actually used it a bit  
in a different project.

It's part of web2 and as such I don't think it's technically made it  
in to a release yet so it might be hard for us to make it a  
dependency, but moving all of windmill to twisted has been an option  
on the table for a long time, for a variety of issues not just this one.

>>
>>
>> Even a proof of concept that works outside of windmill but  
>> accomplishes what we need in python would be fine.
>
> hm.  so...you'd want an example of a third party app starting up  
> Twisted https, ideally via Paste, and hooking itself in?  The Zope 3  
> world almost certainly has one of those hanging around, if so.


What i meant by proof of concept wasn't just a proxy server, but a  
proxy server that actually replied with fake SSL certs for the target  
domain so it could look at the traffic.

Paste has a proxy server but it doesn't exactly work the way that we  
would need it to and it has some outstanding bugs. I actually talked  
with Ian Bicking about this over email already.

Twisted does have an SSL proxy server, but... it's twisted. Moving to  
twisted is a lot of work on it's own, definitely a possibility, but by  
no means an "easy" solution. I'm also not surprised they can do this,  
they have a lot of good abstraction at the socket layer.

My thinking on this right now is that what might be the easiest  
solution is going with twisted. This is a large undertaking and isn't  
on what i would call the "short list". That said, I don't see us  
calling a windmill release 1.0 without SSL support, so it _will_ be  
done.

-Mikeal


More information about the Windmill-dev mailing list