streamed filtering
Hello, in november there was a plan to prototype the stream interface in Perl. I would like to know the status of it. I am particularly interested in new features for the output filter api. I have been missing a way of creating a context for the filter. Thanks in advance! And happy new year! E s t eb a n! :wq - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [mp2] config: directive missing closing '>'
On Wed, 2003-01-08 at 00:56, Dmitri Tikhonov wrote: > > Hi, Simply put, there is a small difference in behaviour (bug) in apache's config parsing code. For now, just put instead of Apache assumes <> containers to always have a value argument, like in . Will eventually be fixed though. > I am in the process of converting to Apache2/mod_perl2. My old httpd.conf > file contains these lines (stuff in the middle omitted): > > - > LoadModule perl_module /usr/libexec/mod_perl.so > > $ServerAdmin = 'admin@'.`hostname`; > > - > > After LoadModule directive, I added this line: > > - > PerlRequire /etc/httpd/conf/startup.pl > - > > (taken straight from ./docs/user/config/config.pod of mod_perl > distribution) and uncommented 'use Apache::compat' line. > > When I start apache, I see this error: > > - > [root@audrey conf]# /usr/sbin/httpd -f /etc/httpd/conf/httpd.conf > Syntax error on line 90 of /etc/httpd/conf/httpd.conf: > directive missing closing '>' > [root@audrey conf]# > - > > I only found this recent thread -- > http://www.mail-archive.com/[email protected]/msg03485.html -- I think > it talks about directive support not being finished (?) Is that > correct? Documentation on section is empty > (http://perl.apache.org/docs/2.0/user/config/config.html#C_E_lt_PerlE_gt___Sections). > > I have no idea what's going on. What am I missing? Is there another set > of documentation that explains this behavior? > > My setup: apache 2.0.43, mod_perl 1.99_07. > > Thanks in advance. > > - Dmitri. > > Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B) http://gozer.ectoplasm.org/F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5 Q: It is impossible to make anything foolproof because fools are so ingenious. perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}' signature.asc Description: This is a digitally signed message part
Re: [mp2] config: directive missing closing '>'
On 8 Jan 2003, Philippe M. Chiasson wrote: > Simply put, there is a small difference in behaviour (bug) in apache's > config parsing code. For now, just put > instead of > > Apache assumes <> containers to always have a value argument, like in > . > > Will eventually be fixed though. Thanks for pointing me in that direction. While did not work as you suggested (produced error 'no handler specified'), it did cause me to grep for this error message, and it is in file src/modules/perl/modperl_cmd.c. I was able to get some information from that code: mod_perl wants directive of the form where Some::Handler actually looks like a valid handler, i.e. has a subroutine called handler(). The module is compiled and handler() is called during config parse time. Unfortunately, I could not figure out how to set Apache directives from that subroutine. Simply setting global $ServerAdmin does not produce the desired effect. Is there a global Apache config namespace or hash? Also, my httpd.conf has things like this: $PerlConfig = " # some directives here. "; I am at a loss as to how I'd go about replicating these dynamically generated directives in the new mod_perl model. Eagerly waiting for suggestions, - Dmitri. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [mp2] config: directive missing closing '>'
My apologies... Need to double-check what I say before I say it. Support for the sections was added after 1.99_07 and will be included in the next release. Sorry for the confusing advice. You might want to give a try at one of the nightly tarballs or at a CVS checkout. On Thu, 2003-01-09 at 01:12, Dmitri Tikhonov wrote: > > Thanks for pointing me in that direction. While did not work as > you suggested (produced error 'no handler specified'), it did cause > me to grep for this error message, and it is in file > src/modules/perl/modperl_cmd.c. I was able to get some information from > that code: mod_perl wants directive of the form > > where Some::Handler actually looks like a valid handler, i.e. has a > subroutine called handler(). The module is compiled and handler() is > called during config parse time. Unfortunately, I could not figure out > how to set Apache directives from that subroutine. Simply setting global > $ServerAdmin does not produce the desired effect. Is there a global > Apache config namespace or hash? > > Also, my httpd.conf has things like this: > > > $PerlConfig = " > > # some directives here. > > "; > > > I am at a loss as to how I'd go about replicating these dynamically > generated directives in the new mod_perl model. > > Eagerly waiting for suggestions, > > - Dmitri. > > On 8 Jan 2003, Philippe M. Chiasson wrote: > > > On Wed, 2003-01-08 at 00:56, Dmitri Tikhonov wrote: > > > > > > Hi, > > > > Simply put, there is a small difference in behaviour (bug) in apache's > > config parsing code. For now, just put > > instead of > > > > Apache assumes <> containers to always have a value argument, like in > > . > > > > Will eventually be fixed though. > > > > > I am in the process of converting to Apache2/mod_perl2. My old httpd.conf > > > file contains these lines (stuff in the middle omitted): > > > > > > - > > > LoadModule perl_module /usr/libexec/mod_perl.so > > > > > > $ServerAdmin = 'admin@'.`hostname`; > > > > > > - > > > > > > After LoadModule directive, I added this line: > > > > > > - > > > PerlRequire /etc/httpd/conf/startup.pl > > > - > > > > > > (taken straight from ./docs/user/config/config.pod of mod_perl > > > distribution) and uncommented 'use Apache::compat' line. > > > > > > When I start apache, I see this error: > > > > > > - > > > [root@audrey conf]# /usr/sbin/httpd -f /etc/httpd/conf/httpd.conf > > > Syntax error on line 90 of /etc/httpd/conf/httpd.conf: > > > directive missing closing '>' > > > [root@audrey conf]# > > > - > > > > > > I only found this recent thread -- > > > http://www.mail-archive.com/[email protected]/msg03485.html -- I think > > > it talks about directive support not being finished (?) Is that > > > correct? Documentation on section is empty > > > >(http://perl.apache.org/docs/2.0/user/config/config.html#C_E_lt_PerlE_gt___Sections). > > > > > > I have no idea what's going on. What am I missing? Is there another set > > > of documentation that explains this behavior? > > > > > > My setup: apache 2.0.43, mod_perl 1.99_07. > > > > > > Thanks in advance. > > > > > > - Dmitri. > > > > > > > > > > Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 > > (122FF51B/C634E37B) > > http://gozer.ectoplasm.org/F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 > > 88C3 A5A5 > > Q: It is impossible to make anything foolproof because fools are so > > ingenious. > > perl > > -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}' > > > > > Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B) http://gozer.ectoplasm.org/F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5 Q: It is impossible to make anything foolproof because fools are so ingenious. perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}' signature.asc Description: This is a digitally signed message part
Re: streamed filtering
Esteban Fernandez Stafford wrote: Hello, in november there was a plan to prototype the stream interface in Perl. I would like to know the status of it. I am particularly interested in new features for the output filter api. I have been missing a way of creating a context for the filter. I've a very basic filter context read/write working, will commit it soon. Then we probably need to add the TIE interface to make it more perlish. Currently it's: $ctx = $f->ctx; $ctx = whatever; $f->ctx($ctx); or may be it should just stay this way. As for prototyping the stream interface for input filters and improving both kind of filters, I didn't have a chance to do so yet. But stay tuned, as we need to discuss things especially with those who have played with filters and not what's missing/awkward/wrong in the current implementation. __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One more mod_perl logo
[Xposting to docs-dev since I don't think many are subscribed to the advocacy list] Davor Ocelic wrote: Check out http://www.linuks.mine.nu/~docelic/modperl_logo.html A variant of the logo, to match the popular mod_ssl, openSSL icons. Very nice, Davor! I think that the choice of background could be different. In your version a dark "modperl" string is going on top of dark background, making it hardly visible. At least if you check the bottom of: http://www.linuks.mine.nu/~docelic/modperl_logo.html the two other logos are making the mod_ names more prominent. Also we have decided to go with "mod_perl" and not "modperl", though the online images weren't updated yet. See the example of the logo on perl.apache.org (left upper corner). Thanks. __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
