Am 21.08.2009 um 23:14 schrieb Dan Korostelev: > 2009/8/22 Shane Hathaway <sh...@hathawaymix.org>: >> Hi Dan, >> >> I'll provide feedback for a few parts of your proposal. > Thanks > >> Few developers care about XML-RPC these days. Most web developers >> are now >> working with REST, JSON, and other similar stuff. It's probably >> best to >> move all XML-RPC artifacts, including those in zope.publisher, to a >> single >> package, so that most developers can safely ignore the XML-RPC code. > > That's a good point. After a quick look, it seems to be easy to move > xmlrpc-related things from zope.publisher and zope.app.publisher to > new zope.xmlrpc package. One problem is how to make BBB imports then. > It doesn't look good to me to make zope.publisher dependent on > zope.xmlrpc for xmlrpc stuff, but moving things without BBB imports > will break applications that currently uses zope.publisher xmlrpc. One > option is to use the notorious "extra" dependencies,
Another option are conditional imports: only import from zope.xmlrpc when it does not lead to an import error. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
