on 10/15/2000 11:47 PM, "Shamil Yahin" <[EMAIL PROTECTED]> wrote:
> After looking at all this I came to the necessity to separate an
> application as an entity that have own properties. Then there can be
> special service that will manage all applications and answer for
> questions like: "give me template paths for the current application" or "give
> me module packages for the current application", and finally "give me this
> named property for the current application". The name for this service
> can be ApplicationRegistry or something like this.
right. sounds like the best approach.
> There are some issues to work out. For example, how applications will
> be registered, which identifier should be but in RunData, who will put
> this identifier in each URI, etc.
It would be cool to use the PATH_INFO URL namespace for this. something
like:
http://www.foo.com/$CONTEXT/servlet/$CONTEXT/$APP/
$CONTEXT == "turbine"
$APP == "scarab"
Then, build it in to Turbine to take advantage of all of that however it is
needed to do that.
Using mod_rewrite...it could be shortened to:
http://www.foo.com/$APP/
> Because of the strict timeline in my project I have not implemented the
> above mentioned approach yet. But we need this functionality anyway,
> and I've included time for that work in my timeline for the next 4
> weeks.
No worries...I just wanted to make sure that I wasn't dropping the ball on
this one. I think it is important.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
