At 10:07 AM 12/11/2000 +0000, Matt Sergeant wrote:
>On Sun, 10 Dec 2000, Jim Woodgate wrote:
>
> >
> > [EMAIL PROTECTED] writes:
> > > You can do the twostage server if you are short on memory, speed is
> > > important and usage of active content is relatively low. Setup a
> mod_proxy
> > > and stripped down apache for port 80 and mod_perl for port 8080 for
> > > example. Proxy certain urls to the 8080 and you are good. Set low number
> > > for the mod_perl items, to avoid thrashing. I'd see where Java is weak,
> > > integration wise like 2 MB per process and not even integrated string
> > > processing.
> >
> > I'm sorry I wasn't more clear in my first response. My main point was
> > not that the common threads I've seen on this mailing list didn't have
> > good solutions. It was that these things come up alot, and although
> > there are good solutions, they typically involve something beyond
> > mod_perl...
> >
> > I've used dbm files and shared memory before, and I find it easier to
> > use the built in thread support in java (like I said IMHO of course :)
>
>Except that won't scale beyond 1 server...
But that's the same thing with IPC shared mem modules yet people still use
them on mod_perl for various tricks. It's still easier in Java to do that
sort of sharing -- at least it is for me. As always, other people's mileage
may vary.
