Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

(tye)Re2: CPANPLUS

by tye (Cardinal)
on Sep 28, 2002 at 06:20 UTC ( #201419=note: print w/ replies, xml ) Need Help??


in reply to Re: (tye)Re: CPANPLUS
in thread To install a module...

Sorry, your claim that CGI.pm isn't for networking is, well, silly.

As for CPANPLUS, if they want to keep "CPAN" in the name, then the primary way they are going to attach to CPAN is via a network. I don't mind in the least if they decide that this is not really the central purpose of the module and call it something having to do with "module management" or whatever.

But the point is that the only modules that don't have "::" in their names should be all-lowercase, that is, pragmas. See Filehandles vs. Packages: And the winner is... for one good reason why.

Other reasons include the "I used CGI" problem. Having a "::" in a module name can avoid a lot of confusion.

        - tye (but I plan to switch to "Person::Tye")


Comment on (tye)Re2: CPANPLUS
Re: (tye)Re2: CPANPLUS
by sauoq (Abbot) on Sep 28, 2002 at 17:56 UTC
    Sorry, your claim that CGI.pm isn't for networking is, well, silly.

    Saying so doesn't make it true.

    CGI.pm isn't for networking. It doesn't contain any networking code. It doesn't read from or write to sockets. It reads from stdin and its environment and writes to stdout. (Under certain circumstances, it will also read or write files.)

    CGI is an interface between server software (specifically an information server) and external programs. The interface defines what information the server makes available to those programs as well as how that information is made available. It also imposes some requirements on the response.

    As it stands now, external programs implementing CGI are required to "understand" some of the underlying protocol. Although this isn't desirable, in practice it is a minimal requirement: a script must output a content header. In some cases, NPH scripts for example, programs are allowed to handle more of the application-level protocol communication rather than just the content.

    CGI is really its own thing. Ironically, the only CGI RFC is for SIP CGI. There has been quite a bit of work done on specifying CGI in general and "WWW CGI" in particular. Unfortunately, the effort has dwindled. I encourage you and anyone that reads this to visit http://cgi-spec.golux.com, join the mailing lists, and offer your support. The problem seems to be that people already think CGI is a standard simply because it is ubiquitous. If enough people show their interest, the author, Ken Coar, will almost certainly pick up the torch again.

    Failing that, please don't suggest that we rename the CGI module Net::CGI. That would be reinforcing the misconception that CGI deals directly with networking, which it does not. Leaving it as a top level module makes the most sense.

    -sauoq
    "My two cents aren't worth a dime.";
    

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://201419]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (9)
As of 2014-11-26 05:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My preferred Perl binaries come from:














    Results (162 votes), past polls