[Zope] WebDAV, Zope, M$ and implications...

[Matt Gregory]

I was just talking to a BEA representative who also happened to do some
consulting at a company I used to work for.

This representative mentioned to me that my former employer (who is one of
the biggest supporters of the Zope corporation due to a HUGE array of zope
and ZEO servers, support contracts, consultants, etc...) just dropped Zope
because of a management feud over WebDAV and M$Office support.  I have not
been able to confirm if this is true, but it sure had an impact on my
current boss.

If  you know about BEA's Portal Server, it uses the WebDAV protocol to
connect to any content management system.  They provide an API which is
supposed to connect to any WebDAV compliant content management system.  He
dropped this remark in a meeting with my boss (after I stuck my neck out and
supported Zope as a good choice for managing our content).  I have already
written a connection pool and library for pulling zope content over an HTTP
connection directly into our JSP pages.  I'm using Zope 2.5, and I think
that my former employer wasn't, so this may no longer be an issue.

I need to know all about Zope, WebDAV, Microsoft office WebDAV and if Zope
and M$ work friendly over that protocol.  How stable is the zope DAV
support, etc...  I'm not under fire yet but I fear that I may soon be.

P.S.  I would also love to grab the names of any Python developers with
extensive Zope experience who want to work potential contracts in Knoxville,
TN.  They could come in handy later when our implementation goes live,
helping me get up to speed on some features, etc...