On 7/20/01 11:15 PM, "Dave Bryson" <[EMAIL PROTECTED]> wrote:
> 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
That is what I was thinking, I don't think there are many other
ways to invoke an application.
> 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.
I think more like an AppManager not a PipeManager. The pipeline used by
the application would be defined in an application descriptor. The
application descriptor would house all the app specific config info
and the pipeline definition would be contained within the app descriptor.
> 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.
We could have a tool that could be controlled from a console that looked
in a directory for new application and they could be configured on the
fly with a web console.
I'm not sure if this would be a service as this would be very specific
to turbine and might be something similar in design to the ServiceBroker
(I prefer ServiceManger). So we would have something called a
ApplicationManager that could load apps from JARs in much the same way
the ServiceManger should be able to load services from JARs. I think
a lot of code could be shared between the ApplicationmManager and
the ServiceManage. Maybe a base Manager class of some sort.
>
> Dave
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
