Correct. The Server and Application scopes only exist on the hardware/CF instance they're on. They can't move. You can have an instance of them on every machine in your cluster and your code can always reference server.myComponent and you'll know it's there - no matter which server you're on.
The Session scope is directly tied to the server instance it was created on. If you create it on Instance A and then on a subsequent request the cluster sent you to Server B you'd be making a request for a session object that doesn't exist. That's the general run down of the problem. Most people solve this by either using sticky sessions or a 'cluster safe' system like Client variables or cookies. Also - in a cluster you can have problems with the Client variables unless every CF instance is configured to use a shared Client variables repository, generally a DB. Cheers, t On Wed, 26 Jan 2005 14:49:35 -0400, Micha Schopman <[EMAIL PROTECTED]> wrote: > I thought the issue was more that CFC's cannot be serialized in current > editions (and thus cannot be transported to another server in the cluster), > and therefore this also affects server and application scope. So this only > affects session scope? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:191874 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
