Hi,
There is one important aspect of mod_sed design (which is borrowed from Sun
Web Server) that I would like to emphasize is that sed code has been separated
from filter code. So sed code itself can be archived in a shared/static library
(let me call it as libsed). mod_sed filter code is just
I have a request,
in mod_sed, if there are multiline commands, specifying them is
cumbersome, It would be nice to have the ability to specify a script
file instead.
|There is one important aspect of mod_sed design (which is borrowed from Sun
| Web Server) that I would like to emphasize is
On Sat, Aug 23, 2008 at 05:28:05PM +0530, rahul wrote:
I have a request,
in mod_sed, if there are multiline commands, specifying them is
cumbersome, It would be nice to have the ability to specify a script
file instead.
I agree. But I think mod_sed should support both. Any votes or
On Wed, Aug 20, 2008 at 6:53 PM, Nick Kew [EMAIL PROTECTED] wrote:
Any thoughts on dropping it in to trunk
Is it best to preserve the current files/filenames (sed.h, libsed.h, sed0.c,
etc.) to better reflect the history of that code, or should the files be
combined/renamed to something that
On Thu, Aug 21, 2008 at 1:53 PM, Jeff Trawick [EMAIL PROTECTED] wrote:
On Wed, Aug 20, 2008 at 6:53 PM, Nick Kew [EMAIL PROTECTED] wrote:
Any thoughts on dropping it in to trunk
Is it best to preserve the current files/filenames (sed.h, libsed.h,
sed0.c, etc.) to better reflect the
| Any thoughts on dropping it in to trunk, with a view
| to including it as standard in 2.4 in due course?
|
| mod_sed is much more than a mere string-or-regexp search-and-replace
What happens to mod_substitute? especially since what substitute
provides seems to be a strict subset of mod_sed ?
On Aug 20, 2008, at 6:53 PM, Nick Kew wrote:
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere string-or-regexp search-and-replace filter:
On 21 Aug 2008, at 13:02, rahul wrote:
| Any thoughts on dropping it in to trunk, with a view
| to including it as standard in 2.4 in due course?
|
| mod_sed is much more than a mere string-or-regexp search-and-
replace
What happens to mod_substitute? especially since what substitute
On 21 Aug 2008, at 13:28, Jim Jagielski wrote:
On Aug 20, 2008, at 6:53 PM, Nick Kew wrote:
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere
Thanks Nick for your initiative to make it part of Apache httpd. I am glad to
contribute to the Apache Software Foundation.
On Thu, Aug 21, 2008 at 02:04:14PM +0100, Nick Kew wrote:
On 21 Aug 2008, at 13:28, Jim Jagielski wrote:
On Aug 20, 2008, at 6:53 PM, Nick Kew wrote:
A little while
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere string-or-regexp search-and-replace filter:
Nick Kew wrote:
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere string-or-regexp search-and-replace filter:
12 matches
Mail list logo
