Subject: Developers of Sympa
List archive
- From: address@concealed
- To: Tim Retout <address@concealed>
- Cc: "address@concealed" <address@concealed>
- Subject: Re: [sympa-dev] Web interface/database usage
- Date: Wed, 25 Mar 2009 08:59:13 -0800
Hi Tim,
Riseup.net currently hosts over 10,000 mailing lists with Sympa, and we have
had to move the list configurations into the database in order for the web
interface to perform well. I have posted patches for this functionality to
the list.
Another thing to consider is using the sympa soap interface within your own
web architecture. It is fairly trivial to do.
More later, as I am at work now. Please get in touch with me if you have any
questions.
Take Care,
Charles Paul
On Wed, Mar 25, 2009 at 11:43:57AM +0000, Tim Retout wrote:
> Hi all,
>
> I am having trouble maintaining patches against the web interface,
> mainly because of its size (16000 lines). For instance, today I am
> adding a new authentication system for a customer, and it is difficult
> to tell immediately whether my changes need to be made only in one
> place. Is there any interest in refactoring the web interface, or using
> a web framework such as Catalyst?
>
> I have also been seeing performance problems - when running with 1000
> lists or so, the 'List of Lists' pages can be very slow to load. I
> believe this is because all the list configuration is on separate
> directories on the filesystem, so a lot of parsing and object creation
> must occur each time. Is there any interest in moving the list
> configuration into the database?
>
> These may well be questions for after sympa 6, but I want to give
> everyone some notice before I go and start writing features that may
> never get merged! :)
>
> Regards,
>
> --
> Tim Retout <address@concealed>
>
-
[sympa-dev] Web interface/database usage,
Tim Retout, 03/25/2009
- Re: [sympa-dev] Web interface/database usage, David Verdin, 03/25/2009
- Re: [sympa-dev] Web interface/database usage, epsas, 03/25/2009
Archive powered by MHonArc 2.6.19+.