[Grok-dev] megrok.rdb

Christopher Lozinski lozinski at freerecruiting.com
Fri Mar 10 10:30:23 CET 2017

I am glad to see this mailing list come back to life.  

Let us start with zope.pulisher. 

I hate autocorrect, it keeps typing hope.publisher.   Maybe I will just leave it like that. 

Take a look at the WebOb website. 

http://webob.org/ <http://webob.org/>

Used by everyone .  100% test coverage.  Presumably no security risks, or they are instantly patched.  

At the very least zope.pulisher should be based on webob. 

Are there any other changes to be made to zope.publisher?

Well the issue is the concepts.  What abstractions does ope.publisher support?  Damn Autocorrect.  

What concepts does pyramid.publisher support?

What concepts does cromlech.publisher support. 

What do I need?  Port 80 and 443.  No webdav.   Maybe eventually the DNS port. 
zope.publisher tries  transactions several times.  I want that part working correctly. 

zope also does authentication.  It used to authenticate everyone.  No nginx caching.  I was quite surprised that the plone community had not fixed that.  So I changed it to only authenticate those who have an authentication cookie.  Or those who click on login.  Or who register.  

Yesterday I discovered that even when logged out, I have a authentication cookie, so it goes against the zope server and not the nginx cache.  Maybe I should have the nginx cache serve requests where the authentication cookie is older than the zope login timeout.

Okay, so that is another set of abstraction.  The point is that I do not want to be fixing these things.  I want to choose software that has a clear published abstraction, and maybe a bunch of switches. 

Which tells me that I should take a closer look at pyramid.publisher.  Although I suspect that at the end of the day, I will find that it is too low level.  Too focused on computer performance, and not on supplying me with the abstractions which I need.  My take on Pyramid is that it is optimized for computer performance, and not for human efficiency. 

On the other hand, maybe Souheil wants to bring cromlech closer to “Grok” so that he can benefit from the user manuals.  

And then I have to comment on Paul’s request as a user.  We are not in the space of large numbers of users.  If I can just get the software I need, then I am a happy man. 

I am also hugely delighted to be reminded of Paul’s user documentation.  Thank you so much.  That is the first thing we need for more users. What do we do to get more users?

So we muddle on with what we have.  And so my part time attention continues to be on upgrading zope.pulisher.  

So paul which parts of zope.publisher do you use?  Is there any chance that the three of us could agree to share and use the same publisher object?

Warm Regards

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/grok-dev/attachments/20170310/2e7b3468/attachment.html>

More information about the Grok-dev mailing list