I like your first idea. What we need to keep in mind, is that focus should be on creating a standard set of frameworks promoting separation, code re-use and abstractions to facilitate real-world application development.
(In a separate thread we will discuss details of the CGI framework i.e. web/cgi addon, but here need to reserve wiki space for it.) To put it in detail, here's a list of all web-related things foreseeable so far that will be hosted in the Wiki: - "Command line and CGI" [MartinNeitzel] http://juggle.gaertner.de/bnp/cgi.html or reference - "CGI and J" http://www.jsoftware.com/jwiki/Guides/CGI (is that jtk's article?) - FastCGI Gudie - SCGI Guide - FastCGI/SCGI script - CGI (framework to be) - JHP framework (to be) - JWebServer framework - Web services (addon) - XMLRPC (addon) JHP needs to be split into CGI and JHP proper parts. So that it references the web/cgi addon. FastCGI/SCGI needs to be re-organized a little. They need to be addons, with only their specific code and simple test examples. But each should include configuration example scripts for various servers, with a note in manifest that their details (the readme or instructions) are in the Wiki. For common CGI handling in terms of parcing parameters, generating output etc. they will have to reference the web/cgi addon. It is proposed to organized the Wiki pages physically: "Command line and CGI" - external link Web/CGI - "CGI and J" Web/FastCGI (guide) Web/SCGI (guide) Addons/web/fastcgi (includes config samples) Addons/web/scgi (includes config samples) Addons/web/cgi link to CGI root Addons/web/jhp link to CGI root CGI root for the framework pages JHP root for JHP framework JWebServer root Addons/web/service Addons/web/xmlrpc All these will semantically be listed on Web technology page, which itself will be located in Technologies list, (as proposed in a separate message): == Basics == - "CGI and J" - "Command line and CGI" == Frameworks == - JHP framework (to be) - CGI (framework to be) - JWebServer framework == General == CGI: - FastCGI Gudie - SCGI Guide - FastCGI/SCGI (addon) XML and Web Services: - XMLRPC (addon) - Web services (addon) The latter we need to cross-reference from the Interfaces technology page. Another related by separate technology is "Net", see JAL categories, dealing with sockets and other ports. It will host for example the Pump script, which should be Addons/net/pump. Other comments below. --- bill lam <[EMAIL PROTECTED]> wrote: > Actually I do not have any particular preference for jwiki structure. However > I > still favour the topic "CGI" to be the current article originally contributed > by > jkt but not as "CGI framework" suggested. > > may be something like this > > Web/CGI (jkt's article) > Web/FastCGI > Web/SCGI > Web/Other_one-page_topics > or > Guides/CGI (jkt's article) > Guides/FastCGI > Guides/SCGI > > or > Guides/CGI (jkt's article) > Guides/CGI/FastCGI > Guides/CGI/SCGI > > If someone doesn't use CGI (in the sense of jkt'article), there is little > reason > why he ever uses FastCGI/SCGI. OTOH he can use CGI/FastCGI/SCGI in the his > own > way, unrelated to the purposed "CGI framework". > > In this context, FastCGI/SCGI is more closely related to CGI than that > between > CGI and "CGI framework". Technically speaking FastCGI/SCGI are not CGI protocol at all, because the do not use command line or pipes, but sockets; they just happen to be called by association "CGI" the same way we call "CGI framework". Otherwise, following this path ASP ISAPI hanlder via dllhost.exe, communicating with the HTTP kernel using pipes or sockets could be called "CGI". > Oleg Kobchenko wrote: > > So we narrow down to a common part: > > (Web as aggregator page linking to all the pages below) > > CGI/Guide > > CGI/... (frameworks) > > JHP/... > > and a couple of possibiities, > > Web/FastCGI > > Web/SCGI > > Web/Other_one-page_topics > > or > > Guides/FastCGI > > Guides/SCGI An important comment was cut off --- Oleg Kobchenko <[EMAIL PROTECTED]> wrote: > Presence of pages under Guides root calls for listing them on the Guides > page itself. But they are also web-related, so they should be on Web. > This leads to duplication, referencial integrity issues, etc. So the > first choice becomes obvious. ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
