Either you become an official Zope committer with write-access to the CVS or by providing reasonable patches, documentation if needed and updated unit tests. Andreas ----- Original Message ----- From: "Brad Clements" <bkc@murkworks.com> To: <zope-dev@zope.org> Sent: Thursday, February 28, 2002 13:35 Subject: Re: [Zope-dev] Zope 2.6 planning - call for contributors!
I went to http://dev.zope.org/Resources/zope_260_plan.html and logged in, but couldn't see any way to contribute comments to this page. I could comment on major projects, but none of them fit my objective.
--
I've modified HTTPResponse and ZServer/HTTPResponse.py to allow for gzip content encoding on a response-by-response basis. I'm mostly using this with xml-rpc, but it could be generalized and combined with a gzipper- cache manager.
I realize that Transfer encoding is really what should be supported, but the fact is that many clients don't handle transfer encoding, but most do handle content-encoding.
How can I contribute this? It'll probably need some tweaking to bring it into "standards".
--
I've modified medusa/ftp_server to allow specifying the PASV port range in the environment.
How do I contribute this?
---
Do I just submit both of these to patch manager?
Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )