Rip out ZServer support.

[icemac]

Open questions/tasks:

• Should zserver directives be removed from etc/example.conf? ← they already have been removed
• Find out if ZApplicationWrapper.__bobo_traverse__ is actually only called by ZServer, see

  Zope/src/App/ZApplication.py

  Lines 45 to 47 in b9a3469

  	def __bobo_traverse__(self, REQUEST=None, name=None):
  	# This is only called by ZServer.ZPublisher.Publish,
  	# as the app in the module_info is used directly.

  ← yes, it is actually used by a ZServer based Zope but not by a WSGI based one.

fixes #592

[dataflake]

Was this not ready for removal?

[icemac]

You are right it can be removed in 5.0 but in another PR.

[d-maurer]

Michael Howitz wrote at 2019-9-9 23:10 -0700:

... -# BBB Zope 5.0 +# BBB Zope 6.0 You are right it can be removed in 5.0 but in another PR.

Please keep "webdav" support (which apparently accidentally was moved into the `ZServer` package).

[icemac]

Zope 4 using WSGI does not support WebDAV. There is #649 track re-enabling it. It would be a huge benefit if Zope 5 could support WebDAV again.
I personally neither have the need nor resources to re-implement WebDAV in Zope, so any help is welcome.

[d-maurer]

Michael Howitz wrote at 2019-9-10 23:19 -0700:

Zope 4 using WSGI does not support WebDAV. There is #649 track re-enabling it. It would be a huge benefit if Zope 5 could support WebDAV again. I personally neither have the need nor resources to re-implement WebDAV in Zope, so any help is welcome.

"WebDAV" used to be a top level package in Zope 2. I assume that it was put below `ZServer` under the (wrong) assumption it were dependent on `ZServer`. Could you move it into a separate "zopefoundation/webdav"? `OFS` and (I think) `ZPublisher` have special handling for `WebDAV`. It would be quite difficult (complex monkey patching) to have `WebDAV` without this special code. In Zope 4, this was dependent on `ZServer` and it therefore risks to get lost with the outphasing of `ZServer`. The dependency should become one of `WebDAV`.

[dataflake]

I'm sure no one would complain if you just went ahead and did this yourself. 😉

[d-maurer]

Jens Vagelpohl wrote at 2019-9-11 03:12 -0700:

I'm sure no one would complain if you just went ahead and did this yourself. ?

I do not yet know how I can move parts from one git repository (including its history) to a different or a new one.

[dataflake]

There's a howto in the GitHub help pages: https://help.github.com/en/articles/splitting-a-subfolder-out-into-a-new-repository

[drfho]

Hi @icemac , @dataflake ,
today our Zope-latest testing system (working with Products.CMFCore) cannot start anymore, because some CMFCore-methods expect a variable OFS.bbb.HAS_ZSERVER.
This comaptibility problem can quickly be solved by providing a reduced module OFS.bbb just for setting the variable:
bbb_py.txt
HAS_ZSERVER = False
Or do you prefer fixing Products.CMFCore?

[dataflake]

Zope master is the precursor of Zope 5. Since this is a major release backwards incompatibilities are OK. A lot of the removed code had already been emitting DeprecationWarnings so it is up to the packages that want to use the deprecated code to get fixed. Fix CMFCore.

[icemac]

@d-maurer I'd prefer to have webdav back here in the Zope repository. I am not sure if it could be used standalone. As you said using it requires some changes in Zope which I do not want to have conditionally again.

Maybe only parts of 24d566b have to be reverted to get it back including its history.

[dataflake]

FYI: Instead of trying to fiddle with some git magic it is sufficient to simply copy the contents of the files in src/webdav from that commit diff (or in case they were updated in ZServer, from there) back into their old location. When you do a git add their history will be right back.

[d-maurer]

Michael Howitz wrote at 2019-9-11 23:17 -0700:

@d-maurer I'd prefer to have `webdav` back here in the Zope repository. I am not sure if it could be used standalone. As you said using it requires some changes in Zope which I do not want to have conditionally again.

I have no objections against `webdav` directly in the Zope repository.