On Sun, 4 Sep 2005, Sam Tregar wrote: > Make sure you know your stuff when you compare CGI to Java and .NET. > There's nothing like a misinformed advocate to damage the reputation > of a technology. Why am I worried? Most server-side Java and .Net > apps use CGI. Also, Java isn't "proprietary" in the usual sense of > the term.
Yes I was going to deal this. My main would be not to rubbish other technologies but to show that perl has not gone the way of the dinosaur and is just as viable as web development platform as the other guys. > > > Ch 2: Architecture of a CGI::App > > > > Model-View-Controller design pattern explained. CGI.pm's inadequacy for > > MVC. CGI::Application is a solution. CGI.pm example rewritten using > > CGI::Application and contrasted. Basic CGI::App features (setup, teardown > > runmodes etc.) introduced. > > I'd also look at how MVC differs from the page-oriented frameworks > like HTML::Mason. Perrin Harkins gave a talk comparing various web-dev > frameworks at YAPC that you might want to look at. > Ok. Thanks for the tip. > > Ch 11: Enhancing interactivity with AJAX > > > > HTML::Prototype and C::A::P::HTMLPrototype > > I hope you have lots of experience to draw on here - these modules > actually provide very little, particularly the plugin. They also > require a very high level of Javascript knowledge which you're > probably not in the right position to grant the reader. > To tell you the truth I have no experience at all! But it wouldn't do for a book with "modern" in the title to not include the buzzword of the moment would it? :-) I'll have to see when I get to that part whether I can do it justice. If not I will leave it out. > > Ch 13: Testing and Optimizing the Application Testing. Ways to > > speed things up discussed. Running under Apache::Registry for > > modperl. C::A::P::Apache > > Testing and optimization have very little to do with each other. I'd > split these up and make a smallish chapter for each. > Ok. > > Appendix B: CGI environment variables > > Please don't! If you feel like you need to provide some CGI reference > then show the CGI.pm and Apache calls to get this data. Showing a > newbie the environment variables leads quickly to re-implemented query > parsers "for speed!!!". > Mmm I don't know...I agree the CGI.pm methods need to be at the forefont but you need to know whats going on underneath. > All in all, it seems like a good idea. The topic has plenty of depth > and a good book could be helpful in getting new people up to speed > faster. Thanks. And I appreciate the comments. I want to do all the writing and development of this out in public so we can end up with something which will make the CGI::Application community proud. -- Jaldhar H. Vyas <[EMAIL PROTECTED]> --------------------------------------------------------------------- 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]
