On Tue, Jul 19, 2011 at 2:02 PM, Jerry Pereira wrote:
> Thats right, i was thinking of avoiding restarts and having single place for
> mapping URIs to classes.
You can get that to some degree if you use Apache2::Reload and avoid
doing anything too strange in your code. The thing is, your best
de
On Tue, Jul 19, 2011 at 12:55 PM, Jerry Pereira wrote:
> I agree, but isn't the Handler tightly coupled to the URI?
Yes.
> rather if i can
> configure the mapping of URI and sub-handlers in a different configuration
> file or database, it will be easier to handle URI changes.
I don't see any ad
I agree, but isn't the Handler tightly coupled to the URI? rather if i can
configure the mapping of URI and sub-handlers in a different configuration
file or database, it will be easier to handle URI changes.
On Mon, Jul 18, 2011 at 3:27 PM, Perrin Harkins wrote:
> On Mon, Jul 18, 2011 at 6:02
On 18 Jul 2011, at 23:02, Jerry Pereira wrote:
> Please let me know of your views. I am not planning to use Catalyst or
> existing frameworks as of now.
Any reason? There are lightweight ones that play well with modern approaches
to plugins and multi-server environments.
On Mon, Jul 18, 2011 at 6:02 PM, Jerry Pereira wrote:
> Single PerlResponseHandler for my application, all requests will be
> submitted to this handler, the handler will then dispatch the request to
> appropriate sub-handlers based on the URI path.
Sounds like Apache2::Dispatch to me.
> I also t
Hi,
I am new to mod_perl and would like to get some suggestion on my current
application design.
Following is the design:
Single PerlResponseHandler for my application, all requests will be
submitted to this handler, the handler will then dispatch the request to
appropriate sub-handlers based o
