Hi Nick, thanks for answering.. im reading your book and surfing some
apache code for hacking.. it has been a nice trip
.. and your book is very rich of knowledge! (without it.. only hacking the
code :s) so thanks for that :)
i've done some nginx modules coding too, and apache it's way more produ
On Wed, 15 Sep 2010 14:57:25 -0300
Fabio Kaminski wrote:
I'm not certain I understand the question, but here goes ...
> and at least for data, i thought use something like [input filter ->
> handler -> output filter]
>
> where the input filter receives a formated string and parse into a intern
Ben,
I know thats not the traditional way to do it.. and the way i used to do it
too.. but i wanna to scale and use only the resources i really need, been
fast as possible.. so i think nothing better than be apache itself..
besides i see a lot of optimizations and freedom (like caching, or routin
Fabio, do you need a module for this? It sounds like it better belongs
in an application server like Tomcat.
since SetHandler directive "disable" my filter when fired.. does it disable
all others filters, like cache and session?
On Wed, Sep 15, 2010 at 2:57 PM, Fabio Kaminski wrote:
> Hi all,
>
> im working with apache modules on apache 2.3 for direct application
> development..
>
> and at least for dat
Hi all,
im working with apache modules on apache 2.3 for direct application
development..
and at least for data, i thought use something like [input filter ->
handler -> output filter]
where the input filter receives a formated string and parse into a internal
object struct.. the handler get it
