content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: http://techdocs.postgresql.org/v2
Date: Fri, 16 Jan 2004 21:56:10 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B87204CA@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] http://techdocs.postgresql.org/v2
Thread-Index: AcPceXZz8Z2Z+yqKSICFfdh+6xrc5wAAVlfg
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <josh@agliodbs.com>,
	"PostgreSQL Web Development Mailing List" <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Josh Berkus [mailto:josh@agliodbs.com]=20
> Sent: 16 January 2004 21:40
> To: Dave Page; PostgreSQL Web Development Mailing List
> Subject: Re: [pgsql-www] http://techdocs.postgresql.org/v2
>=20
> Justin's and my problem with Plone was that is was=20
> intolerably slow on updates and administrative interfaces;=20
> some of the admin screens took over a minute=20
> just to load.   And this was with just him, me & Elein on it.

The only really noticable speed issues I saw whilst playing were local
network issues. I editted one page and it certainly wasn't noticably
slower than our other php admin interface.

>=20
> Also, the plone "look" says "Plone" not "PostgreSQL".=20=20=20
> However, if it gets=20
> something up and running in a hurry, I can certainly live with that.
>=20
> If we've got it performing better now, it's worth a 2nd look.

I think so. It looks nice, and seems quite usable and maintainable. Like
I said, the only real issues I noticed were the lack of access controls
(users should not be able to modify config nor (imho) content) and the
seemingly useless calendar (is that some kind of 'see this folder how it
was on xx-xx-xxxx' control?)

Regards, Dave.