Geoffrey Young wrote:
I feel I need to interject here. _all_ of the points you raise to this point are well covered in the mod_perl developer's cookbook, which has been available since 02/2001. in fact, that's why we wrote it - both to address many of the things the mod_perl community had learned since the eagle book was written, as well as take the "access to the C API in Perl" road. we hardly even mention Registry or CGI (but we do mention how to subclass RegistryNG :) and that was very, very on purpose.
the unfortunate situation is that the cookbook suffers from lack of exposure
(and sales, for that matter) - you obviously understand mod_perl and are
participating on the list, yet you still didn't know that your issues are
(and were) well covered with available documentation.
Really? It hasn't sold well? I've used it a lot -- my copy is a bit beat up.
Well, from one satisfied reader, here's a big "Thank You!" to Geoffrey, Paul Lindner, and Randy Kobes for writing that book!
Don't you mean 02/2002? My copy says first printing January 2002. Also, maybe the publisher (SAMS) hasn't given you the support you deserve.
On the marketing front, doesn't Amazon use mod_perl, at least partially? Maybe you could get some mention or a logo on their site, ya know, as a way to support the community? Maybe some Easter egg that pops up if you do a specific search, i.e. something that engineers would have fun passing around?
Take care,
Kurt Hansen
P.S. I also have the Eagle book and Practical mod_perl and am very grateful for those as well! Especially recently during a move to Apache2/mod_perl2
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
