Tapestry Application - Single or Multiple

[Dylan Spence <dy...@comcast.net>]

I am trying to work out the architecture for an Extranet and/or Intranet site.  How is this commonly handled, with regards to Tapestry applications?  

I saw that most of the applications deal with one application at a time.  So should I view the Extranet as an application, or should I make multiple Tapestry servlets up in the web.xml for each one of the systems that will comprise the Extranet system?

Re: Tapestry Application - Single or Multiple

[Erik Hatcher <er...@ehatchersolutions.com>]

I think the solution is not clear-cut.  More than likely, I'm guessing, 
the deciding factor will be how you handle security.  If you are using 
J2EE declarative web security, separate applications is the best way to 
accommodate I've found.

But if you have your own security system, then you have more control.

If you have an intranet site, though, perhaps it should be on its own 
firewalled server?

	Erik


On Mar 17, 2004, at 1:50 PM, Dylan Spence wrote:

> I am trying to work out the architecture for an Extranet and/or 
> Intranet site.  How is this commonly handled, with regards to Tapestry 
> applications?
>
> I saw that most of the applications deal with one application at a 
> time.  So should I view the Extranet as an application, or should I 
> make multiple Tapestry servlets up in the web.xml for each one of the 
> systems that will comprise the Extranet system?


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org