I know about ASSP 2.0 . However I'm not talking about multithreading. I'm talking about 2 separate daemons (working on different ports). 1 daemon on a new port for ASSP web interface and all the features included like tail log , asspblock and resendmail and so on , and another daemon dedicated only to process email (a light ASSP which should read and process ONLY assp.cfg without all the work related to assp web interface , and other stuffs). ASSP 1.x can run also on old servers and I have seen running on VPS in an excellent way . multithreading requires a super server , is not for all (for now).
> ASSP development mailing list <assp-test@lists.sourceforge.net> > schreibt: > >> My stupid idea is ... is not better to have 2 daemons , 1 daemon for >> ASSP web interface and all the features included like >> tail log , asspblock and resendmail and so on , and another daemon >> dedicated only to process email ? >> > > > It is a stupid idea, because we already have a multithreading version. > > Run ASSP 2.0.0 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
