Here's a few questions I have about putting this
all together. I kinda want to see how others are thinking
about this. ( i've added my thoughts that are formed by Jason's notes and
Catalina )
1. What would be a good way to address a subapp in Turbine?
<my thought> If we use XML to configure subapps why not use
something similiar to the approach used for webapps. Each subapp
could be addressed via it's own "context" added on to the URL.
For example: If i have two subapps called "subapp1" and "subapp2",
the URLs would look something like this:
http://mydomain.com/turbine/servlet/turbine/subapp1
http://mydomain.com/turbine/servlet/turbine/subapp2
2. How can these subapps be mapped to their pipelines?
<my thought> Again this could be specified in the XML.
The Turbine Servlet could use something like a "PipeManager".
The PipeManager could load it's mappings in init() and be keyed by
URL "context" as mentioned above. Each Pipeline would map to a
subapp. Each Pipeline would contain it's own module loader and
an aggregation of valves. Again *all* of this being configurable in XML.
3. How could subapps be loaded and configured at runtime?
<my thought> Each subapp would use a snippet of XML for the pipeline and
valves. This snippet would be placed in a standard place ( like web.xml
is under WEB-INF ). A Turbine service could be configured to monitor
a "hot" directory for changes and load the changes into the
PipeManager.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
