This is the summary for test reports received on the
zope-tests list between 2011-07-02 00:00:00 UTC and 2011-07-03 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
Hi Hanno,
I haven't checked deeply, but the change below seems to break
Products.ZSQLMethods. At least there is an import in
Products.ZSQLMethod from this location. And we depend heavily on it...
Since you're already around that piece of code, would you mind moving
it over there and releasing a n
On Sun, 2011-07-03 at 17:44 +0200, Hanno Schlichting wrote:
> > I don't have any skin in this game, but FTR, Mike Bayer isn't feeling
> > all that confident about Beaker's sessioning component (or so he has
> > told me). Beaker was originally made as a caching component, and had
> > sessioning jam
On 2011-7-3 17:48, Martin Aspeli wrote:
> 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
On 3 July 2011 16:44, Hanno Schlichting wrote:
> On Sun, Jul 3, 2011 at 7:09 AM, Chris McDonough wrote:
> > Zope still needs to the virtual host monster (or something like it) even
> > with the WSGI publisher; there's nothing equivalent in the WSGI world
> > (unless you could repoze.vhm, which i
On Sun, Jul 3, 2011 at 7:09 AM, Chris McDonough wrote:
> Zope still needs to the virtual host monster (or something like it) even
> with the WSGI publisher; there's nothing equivalent in the WSGI world
> (unless you could repoze.vhm, which is essentially just the virtual host
> monster, and probab
