[JOB] looking for one
hiya. time to pimp myself out again! i'm looking for full time or contract work beginning in july. the catch of course is that i'll need to be able to telecommute from melbourne, australia at least 50-75% of the time. i have no special requirement for the remainder :) i'll be in san francisco starting the 1st of july for ~3 months, so i can be onsite anywhere in north america pretty easily during that time period. travel elsewhere is not out of the question. see http://www.maz.org/bcm/resume.txt for more details. thanks!
i use linux+apache. how to create a cgi-bin directory for Virtual Host?
my system is build on linux+apache now i'm create virtual hosts.i change the config file (/opt/apache/conf/httpd.conf)like this: # get the server name from the Host: headerUseCanonicalName Off# this log format can be split per-virtual-host based on the first fieldLogFormat "%V %h %l %u %t \"%r\" %s %b" vcommonCustomLog logs/access_log vcommon # include the server name in the filenames used to satisfy requestsVirtualDocumentRoot /www/hosts/%0/VirtualScriptAlias /www/hosts/%0/cgi-bin now i try to browse the virtual host ,i can get http://www.1.com/test.htm (which is in /www/hosts/www.1.com/,) but can not get http://www.1.com/test.pl .(which is in /www/hosts/www.1.com/cgi-bin),the system can't find the file. yet i can get http://localhost/cgi-bin/test.pl,(which is in /opt/apache/cgi-bin),why? by the way,i need create many virtual host,so i must do dynamic creating like above.
Re: comparison of templating methods?
will trillich wrote: > HTML::Mason > Template-Toolkit These are only two I have much experience with. I've found both to be well written, stable and well supported. TT makes it easier to separate the logic from the presentation layer IMHO. But every time I code a project in mason I find myself smiling and thinking 'This is fun', at least occasionally. Projects seem to come together _much_ faster with Mason, though overall coding time isn't much different. With Mason you have to work harder if you want to separate logic & presentation, but its fairly straightfoward if you put some thought into your component design ahead of time. So typically, if I need skinability, or if I need to give edit capability to html'ers with no perl but light scripting ability I use TT, otherwise I use Mason. J
Re: comparison of templating methods?
will trillich wrote: > HTML::Mason > Template-Toolkit These are only two I have much experience with. I've found both to be well written, stable and well supported. TT makes it easier to separate the logic from the presentation layer IMHO. But every time I code a project in mason I find myself smiling and thinking 'This is fun', at least occasionally. Projects seem to come together _much_ faster with Mason, though overall coding time isn't much different. With Mason you have to work harder if you want to separate logic & presentation, but its fairly straightfoward if you put some thought into your component design ahead of time. So typically, if I need skinability, or if I need to give edit capability to html'ers with no perl but light scripting ability I use TT, otherwise I use Mason. J
Re: comparison of templating methods?
will trillich wrote: > HTML::Mason > Template-Toolkit These are only two I have much experience with. I've found both to be well written, stable and well supported. TT makes it easier to separate the logic from the presentation layer IMHO. But every time I code a project in mason I find myself smiling and thinking 'This is fun', at least occasionally. Projects seem to come together _much_ faster with Mason, though overall coding time isn't much different. With Mason you have to work harder if you want to separate logic & presentation, but its fairly straightfoward if you put some thought into your component design ahead of time. So typically, if I need skinability, or if I need to give edit capability to html'ers with no perl but light scripting ability I use TT, otherwise I use Mason. J
Re: Apache pnotes
On Sat, 9 Jun 2001, Jamie Krasnoo wrote: > The Eagle Books explanation of notes isn't very clear. Could someone point > me to a page that explains it somewhat better? In what situation would it be > beneficial to use them? You use notes (or pnotes) when you want a kind of global variable that is localised to the request, but also accessible to sub-requests. For example, Apache::Request stores it's current instance in pnotes, so that it's guaranteed to be unique to that request. If it were stored in a global, it would be the same apr object in subrequests. Use pnotes instead of notes when you either need to store a perl object, or need to store binary nulls. -- /||** Founder and CTO ** ** http://axkit.com/ ** //||** AxKit.com Ltd ** ** XML Application Serving ** // ||** http://axkit.org ** ** XSLT, XPathScript, XSP ** // \\| // ** mod_perl news and resources: http://take23.org ** \\// //\\ // \\
