Path: news.cs.au.dk!not-for-mail From: "Sascha Kimmel" Newsgroups: comp.lang.beta Subject: Re: BETA for CGI Date: 21 Jun 2000 08:29:55 -0000 Organization: University of Aarhus, Department of Computer Science (DAIMI) Lines: 42 Approved: mailtonews@cs.au.dk Distribution: world Message-ID: <20000621082955.10567.qmail@noatun.mjolner.dk> Reply-To: "Sascha Kimmel" NNTP-Posting-Host: daimi.cs.au.dk X-Trace: xinwen.cs.au.dk 961576877 352527 255.255.255.255 (21 Jun 2000 08:41:17 GMT) X-Complaints-To: news@cs.au.dk NNTP-Posting-Date: 21 Jun 2000 08:41:17 GMT Xref: news.cs.au.dk comp.lang.beta:12473 > -----Original Message----- > From: Flemming Gram Christensen [mailto:gram@mjolner.dk] > Sent: Tuesday, June 20, 2000 4:15 PM > To: usergroup@mjolner.dk > Subject: Re: BETA for CGI > [...] > > Using distribution or standard TCP communication it is not hard to > make your own dedicated server. You can use coroutines to handle each > 'web-session'. I doubt that this is very efficient and secure in comparison to multithreaded web servers!? AFAIK BETA does not use THREADS for coroutines, because this is only *emulated* in BETA!? Apache e.g. IS multithreaded on Windows. > The web-server can use a small program, written in > Perl, say, to communicate with the BETA programmed server. Yes, you can build such a pretty HTML administration as e.g. Netscape Enterprise server has :) BUT instead of Netscape you should ALWAYS be able to change settings via the HTML Interface, Netscape has some functions which you can edit/set through the HTML interface but not reset/remove through the interface, making it necessary to edit some config files manually :( > To my knowledge at least two projects has been done this way. And let me guess: if someone wants to implement such a thing he has to reinvent the wheel again and again because the sourcecode of these projects is NOT included in BETA itself? Regards, Sascha Kimmel