Hi Ron & All -- 

> > My thoughts about the name (in loose order of preference):
> > WWW::ImageServer
> 
> My preference too, but then I did not think too hard...
> 
> > Apache::ImageServer
> 
> Apache? Will it be crippleware, ie refuse to run on other web 
> servers (not that 
> there are that many choices)?
> 
> > CGI::Application::ImageServer
> 
> Understandable choice, but my policy these days is to use 
> names which describe 
> what a module does, rather than describe what components were 
> used to provide 
> the module's services.


How about:  

  HTTP::ImageAbuser


Too obscure?  Too cute?

As a few others pointed out, most of the "WWW::" space is clients, so
"HTTP::" might be a better place.  Also, this will work on non-Apache
servers (although, I'd like to make it work particularly well in
Apache).


-Jesse-


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to