Shane Hathaway wrote:
> 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.
+1 on this general direction.
>> IFTPDirectoryPublisher interface - not sure what's this and where is
>> it used. Probably should be moved to zope.publisher.interfaces.ftp as
> FTP is in the same boat as XML-RPC. Today, very few developers care to
> provide a dynamic FTP view of anything. WebDAV usually wins over FTP
> because adding SSL to WebDAV is easy. All FTP artifacts should move to
> a separate package.
+1 as well.
I've recorded this information in the Zope Toolkit decisions document,
just so we know where we're heading.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -