From: Claes W. <kl...@hy...> - 2002-10-09 14:51:47
|
Folks, When I was setting up this list I had a look at mailman which is mailing list software. (As it happens, it is the software they use at sourceforge) Anyway, they use a cgi interface to a webserver. I suspect there are a lot of tools out there that interact with webservers over cgi. We should do a cgi interface. Another question: How do website builders typically do to combine, say dreamweaver and php ? /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.hyber.org -- everything is under control |
From: Luke G. <lu...@bl...> - 2002-10-09 16:09:28
|
Claes Wikstrom <kl...@hy...> writes: > Folks, > > When I was setting up this list I had a look at mailman which is > mailing list software. (As it happens, it is the software they use > at sourceforge) > > Anyway, they use a cgi interface to a webserver. I suspect there are > a lot of tools out there that interact with webservers over cgi. > We should do a cgi interface. Another direction would be to make Yaws embed'able as an Apache module. I'm sure you don't like the idea of putting Apache in the driving seat :-) but it would be a direct way to get interoperability with all the other things people do (CGI, mod_*, etc). I'm (wildly) guessing things like mod_perl are more important at a lot of sites than CGI. I saw a pretty minimal apache module recently. It basically farms out requests in a CGI-like way but through a persistent socket instead of a subprocess. The program is written for Lisp plugins to Apache, but I don't think the C/apache part is actually lisp specific. It's "mod_lisp" on http://www.fractalconcept.com/ and might make a nice template. Actually, there're some pretty interesting looking modules on http://modules.apache.org/ > Another question: How do website builders typically do to combine, say > dreamweaver and php ? I shudder to think :-) I've heard some stories about doing this with Java, though this is going back a few years. The idea was to do the pages in Dreamweaver and include some "magic" tags (META maybe) that signal where the java program should fill in details during post-processing, e.g. around an empty table. Cheers, Luke |
From: Mickael R. <mic...@er...> - 2002-10-09 16:19:56
|
Luke Gorrie <lu...@bl...>: > Claes Wikstrom <kl...@hy...> writes: > > > Folks, > > > > When I was setting up this list I had a look at mailman which is > > mailing list software. (As it happens, it is the software they use > > at sourceforge) > > > > Anyway, they use a cgi interface to a webserver. I suspect there are > > a lot of tools out there that interact with webservers over cgi. > > We should do a cgi interface. > > Another direction would be to make Yaws embed'able as an Apache > module. I'm sure you don't like the idea of putting Apache in the > driving seat :-) but it would be a direct way to get interoperability > with all the other things people do (CGI, mod_*, etc). I'm (wildly) > guessing things like mod_perl are more important at a lot of sites > than CGI. I think what is cool about yaws is that you get high performance without the burden of writting an Apache module. I suspect that lying the two stack will deteriorate the performance of the system. This might be what you are looking for (Mod_erl): http://www.rfc1149.net/devel/mod_erl.html.en Cheers, -- Mickaël Rémond |