Skip site navigation (1) Skip section navigation (2)

Re: Todo for 'portal', programmers perspective

From: Alexey Borzov <borz_off(at)cs(dot)msu(dot)su>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-www(at)postgresql(dot)org
Subject: Re: Todo for 'portal', programmers perspective
Date: 2004-01-15 16:58:39
Message-ID: 4006C6BF.802@cs.msu.su (view raw or flat)
Thread:
Lists: pgsql-www
Hi!

Robert Treat wrote:
>>>1) If all the static content (i.e. the content that does not change
>>>often) is stored in the database and is editable only through 
>>>web-interface then there is a bottleneck: the person who 
>>>gives access to web-interface. If the interface is not robust 
>>>enough to let not-quite-trusted people use it, then the 
>>>bottleneck is even more narrow. On the other hand, if the 
>>>content is available in public CVS, then every one may check 
>>>it out and edit it and later submit for inclusion.
>>
>>The same bottleneck applies either way as those with access to the admin
>>interface are basically those with cvs commit access. Still, CVS does
>>give more convenient read-only access than the web does.
>>
> 
> 
> I'd like to point out that from a management standpoint, I think we've
> been fairly responsive when it comes to news & events, so I don't see a
> bottleneck there. On top of that, ISTM that it is easier to for end
> users to submit news and to get it approved if its in a web/db based
> system. 

I want to once again point out that this applied to static content, not 
to news and events which should of course be managed through web interface.


pgsql-www by date

Next:From: Peter EisentrautDate: 2004-01-15 17:29:59
Subject: Re: Requirements for updated site
Previous:From: Alexey BorzovDate: 2004-01-15 16:56:47
Subject: Re: Todo for 'portal', programmers perspective

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group