Ari Halberstadt wrote:
>
> B. use separate JVMs launched in manual mode for each user -- this is,
> IMHO, the only reasonably safe solution for paranoid folks, because it is
> the only solution that uses the OS's protections.
>
> I haven't actually ever implemented solution B, but I think you'd need to
> setup separate virtual hosts for each user so that you could specify a
> separate ApJServProperties file for each user. (After writing the following
> example, I (again) realized that the best way to do this is to give each
> developer their own private Apache webserver running on the developer's
> assigned port, rather than mess with virtual hosts and a centralized admin.)
<gruesome details snipped ;) >
If you're using manual mode, why is all this necessary? Isn't the config
file passed as a parameter to the wrapper? Don't you just need seperate
ApJServMount directives connecting to different ports on your webserver?
Eg, the only Apache JServ lines in httpd.conf would be:
ApJServManual on
ApJServMount /aliceservlets ajpv11://localhost:9001/servlets
ApJServMount /bobservlets ajpv11://localhost:9002/servlets
And then just start the wrapper manually, under the users' names,
passing a config file in their home directories?
I'm sure I may be wrong - I havne't thought about the details. But I
honestly didn't think it was as hard as you made it out to be. I didn't
think that the ApJServDefaultPort and ApJServConfigFile options applied
in manual mode, because (I thought) they were just passed to the
wrapper.
The reason I ask was that I was planning on doing exactly this when I
roll out a servlet-based application I've been working on.
Just my 0.4 nickels,
Stuart.
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
