For me, the reloading of the Application scope would be disastrous given the size and amount of traffic on the site I'm looking to do a FarCry implementation. With as long as this process takes, requests would build up until overloading and crashing the server. Any error or interruption is unacceptable. Perhaps when new types or rules are deployed, it would have to be done on a clustered application, taking each instance out of the cluster to update individually. This brings up another question... how do you cluster a FarCry install? I imagine you would need to force the webtop to one instance. I understand there are several large FarCry implementations out there, so I know these concerns have been dealt with.
Thanks for any feedback you can provide about your experience -Nick On Feb 4, 2009, at 11:19 AM, Mark Jones wrote: > > I was expecting that we would have to reload the application to accept > new types/rules, but I wasn't expecting that to cause issues beyond > the time it takes to actually reload the application. What kind of > side-effects should I expect from reloading the app scope on a > production site? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
