"Paul Jordan" <suppressed> wrote: > Jon Jensen wrote: > > You can scale out to multiple > > Interchange servers with one catalog per IC or many. The key is > > getting a shared session backend that can handle the load. And until > > you hit fairly high traffic levels, that's not too hard. > > > That makes me feel better. I think unless someone brings up a good point > otherwise, i'll use a single catalog as it makes life much simpler in > most respects. > I have to agree. The whole thing sounds essentially like one application, so I'd put the whole lot into one website - especially if you want to navigate between subsystems, and access all areas, using a single login session. Multiple Interchange instances can be clustered over multiple machines to spread this one website's load, if required. -- _/ _/ _/_/_/_/ _/ _/ _/_/_/ _/ _/ _/_/_/ _/_/ _/ _/ _/ _/_/ _/ K e v i n W a l s h _/ _/ _/ _/ _/ _/ _/ _/_/ suppressed _/ _/ _/_/_/_/ _/ _/_/_/ _/ _/ _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.