> but I thought that GUI request were server asynchronously so > the main ASSP loop (i.e. email serving) wasn't impacted by > webgui
> Yes and No. The MainThread (MainLoop) does nothing else than listen on all > defined listeners and transfers SMTP connections to the workers before the > connection is accepted. So processing the mails, is asynchronously to the > GUI - getting new connections is not. hmm... I see now; I thought the whole network I/O (listen/accept) was handled by a single thread which then was passing the connections to the workers but now I see it's structured in a different way... ok, at least now I know :) > In addition to that, he is monitoring the SMTP-workers (not realy much > to do), doing the output to STDOUT,STDERR and SYSLOG - and is > doing all the Web-Stuff. For normal web actions this does not matter, > because only the action buttons are doing requests to the web port. Yes, once the HTML has been sent to the client browser ASSP will get back to its regular duty and will just be "called" again in case one hits the "apply" button or one of the "edit" ones or in any case clicks on a link which generates a new web request; yet, in case one tries to edit a "big" file ASSP may look "stuck" for a while... won't be a somewhat better approach having the web GUI running in a separate thread ? (just thinking loud, nothing more !) > Only the autorefresh "SMTP connection" screen will slow down the > MainThread (and Workers) more as a bit, because this screen > refreshes every second and the request impacts also to all Workers, > because they have to collect and to transfer detail status information > to the MainThread. The autorefresh in "Maillog Tail" and the "Worker > Status" will not impact so/too much. well... the GUI thread may also handle this... although I'm not sure it would be possible since the thread would then need to access data/infos which sit inside the main process... hmmm.... > All other actions, like DBImport/DBExport, LDAPCrossCheck, > BlockReports and some more, that could be initiated by the > GUI are transfered to the MaintThread (10000). crisp and clear, thanks :) ! Uh... and btw v2 is still happily running on that other system... ok, it has plenty of RAM and CPU power now and that machine hasn't so much connections but it seems to be ok; will leave it running and we'll see what tomorrow will bring :D About the SF release... I think that it may be a good idea to start by releasing a first v2 as a "pre-release/beta" version and to add to it some "release notes" (see the button in the SF download interface) containing infos about all the needed pre-requisites that is, not just perl version and modules but also a bare minimal h/w config (ram, disk space, cpu...) so that people won't try to install it on a 486sx with 640Kb RAM and then come back screaming since "it's not working" <grin> ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
