> > > > > recommended.
> > > >
> > > > I strongly recommend the opposite for production
> > > > environments.
> > >
> > > But only on a "single site" environment? Doesn't "trusted
> > > cache" cause hassles on servers with multiple sites?
> >
> > Not in a production environment - you can have as many
> > virtual servers on your machines as you want. By "production
> > environment", I mean "servers where you put finished builds
> > of production applications", not "servers where you do development
> > and maintenance, as well as host production applications".
>
> Lots of web hosting companies use multihomed servers. That
> setting must be turned off for multihomed servers. I haven't
> seen a recommendation from MACR that multihomed servers
> shouldn't be used in a production environment. While it may
> be sensible for a major app to have its own server or
> cluster of servers, CF can be used for small sites too that
> don't need (and can't afford) an entire server to themselves.
This has nothing to do with the number of virtual servers and everything to
do with how often code changes on said servers. You can certainly use
trusted cache with multiple virtual servers, as long as no one's changing
code on any of them. I worked in an environment just last week with about
three hundred virtual servers, in which trusted cache was used. Macromedia
does recommend the separation of production, staging and development
environments - it's explicitly mentioned in their courseware.
Again, when I use the phrase "production environment", I mean something
pretty specific. Using separate J2EE server instances, it is possible to
separate production applications from development ones to some degree.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
