<br><br><div class="gmail_quote">On 3 July 2011 16:44, Hanno Schlichting <span dir="ltr"><<a href="mailto:hanno@hannosch.eu">hanno@hannosch.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Jul 3, 2011 at 7:09 AM, Chris McDonough <<a href="mailto:chrism@plope.com">chrism@plope.com</a>> wrote:<br>
> Zope still needs to the virtual host monster (or something like it) even<br>
> with the WSGI publisher; there's nothing equivalent in the WSGI world<br>
> (unless you could repoze.vhm, which is essentially just the virtual host<br>
> monster, and probably doesn't need to live in middleware; no one uses it<br>
> except people who use repoze.zope2).<br>
<br>
</div>I'm expecting us to use repoze.vhm. But I've left the VHM in the code,<br>
so it's easy to install one if you still need it. For some time I<br>
expect Plone to install a VHM as part of its installation process.<br>
<div class="im"><br>
> I don't have any skin in this game, but FTR, Mike Bayer isn't feeling<br>
> all that confident about Beaker's sessioning component (or so he has<br>
> told me). Beaker was originally made as a caching component, and had<br>
> sessioning jammed into it quite late; nobody is really maintaining the<br>
> sessioning component of it now.<br>
<br>
</div>Well, if I can choose between modern unmaintained code from Mike Bayer<br>
and stone-age unmaintained code from Zope, it's still an easy choice<br>
;-)<br>
<br>
And looking at the basics of what Beaker does here, it's still much<br>
more useful and of better quality than what we have in Zope 2.<br>
<br>
If there's any other non-framework-specific session machinery out<br>
there, we could use that as well. But I think most other stuff is tied<br>
into Django.</blockquote><div><br></div><div>FWIW, we have a high-performance, high-load application in production on Plone 4 with collective.beaker relying heavily on sessions, and I'm not aware of any problems with it. We use the memcached backend across two physical servers and a large number of Zope clients.</div>
<div><br></div><div>Martin</div></div>