drieux wrote: > On Friday, Nov 7, 2003, at 10:11 US/Pacific, Wiggins d Anconia wrote: > [..] > > Thank you for putting this so eloquently, to back it up with the most > > simple example of all though.... remember images, that a majority of > > web > > sites use these days, are distributed over that very protocol right > > under our noses! > [..] > > Interesting, hadn't thought about the 'image' side of the > problem. Rather I was thinking in terms of what some would > be calling 'web proxying' and/or 'distributed computing' > where we just happen to be using HTTP as the session layer > hence 'technically' the 'web_server' at the other end of > the socket connection 'could' dish up "web pages" rather > than, well, just be the 'bridge' between the HTTP Request > and the specified URI thingus, which turns out to be a > piece of Perl CGI code, that doesn't have to be god's > brightest crayon in the box, since it merely has to know > whether the 'parameters' passed to it are 'kosher' before > it invokes some code on that box...
Hmmm, these sound more interesting than feeding toys. My point remains, though, that this is a whole different world than standard Web-based programming. As you point out yourself, the connection is only incidental. Therefore, I still don't see why this should be an issue in the selection of tools for the handling of traditional Web=based interactive content. Perl has many APIs, for many purposes. I personally don't like using CGI.pm for generating Web conent. This I do by hand, checking the generated html source and its rendered appearance throughout the process, because I think that the appearance of both is important. I strongly agree with the design goal of XML that source should be human-readable and clear. I would add ergonomically sensible to the standards. Parsing form data, the subject of the OP, is a different matter. CGI does a very solid job of abstracting the details of delivery format, and rendering the parameters to the application. What more do you need from a CGI module? For other purposes, you can use other modules. [snip -- gettin' wa-a-a-ay out there, dude!] Joseph -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
