[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Request handling using routes, containers, (internal) services
- Subject: Re: Request handling using routes, containers, (internal) services
- From: John Locke <..hidden..>
- Date: Mon, 22 Jun 2015 15:16:03 -0700
On 06/22/2015 02:53 PM, Erik Huelsmann wrote:|
In the other thread, John mentioned the structure that web
apps are growing to in general to have these components to
facilitate growth beyond a certain size:
patterns we're discussing I'm seeing put in widespread
use. I'd say those 3 things are crucial for us to
define/decide how we're going to implement (and perhaps
find some Perl framework to assist if those we're
currently using are insufficient):
container to make it easy to register and load services
object (which needs to include the definition of how to
So, I'm now thinking how we can apply these concepts to
LedgerSMB with or without the context of using Plack and/or
Starman. I'm imagining that we will have to handle a certain
amount of it ourselves internally and that we possibly could
hand off some of it to Plack's middleware modules.
What I've been thinking about for some time now is that
we might want to virtualize our current module names 'aa.pl
into routes. For aa.pl
, there really are physical
files, but for other routes, we may not want to handle the
route processing the same way.
Is this something that we need to address "now" (as in:
design it asap and simply continue working on the code base,
but use this as a paradigm for all code that's being
I don't have an answer to that specific question...
But most webapps I've worked with have a single endpoint that
receives all requests. The webserver reroutes any paths that don't
exist on the disk to that endpoint.
Given that all of those little module name endpoints we currently
have are copies of one of two different actual endpoints, it does
seem like we should be able to pretty easily eliminate those... and
just make the single remaining endpoint smart enough to know which
way to handle the request...
I would assume Starman could handle something like that?
For Drupal, Apache first looks for a file on the disk... if it
doesn't exist, it rewrites the path to /index.php?q= (and then adds
the original path). This is done internally, not as a redirect, so
the browser never knows...
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
Ledger-smb-devel mailing list