> I suppose that what Matt was referring to, when talking about stateful > CFCs > scalability issue, is that you cannot use session replication if you put > CFC > in session (because for the moment, CFC are not serializable). > I was referring to the state of a CFC being persisted outside of shared memory. The amount of overhead required to instantiate and reset the state of a CFC is quite high.
> The best example is macromedia.com which extensively uses CFCs on the > "model" layer (with View as ColdFusion pages or Flash applications). > I suppose they also use CFC in session scope, don't you Sean? > Why is Macromedia.com a good example? Who says Macromedia.com is scalable? There is no publicly available information for anyone to be able to determine if Macromedia.com is scalable, so I think you are just assuming. Based on the publicly available information about the hardware behind Macromedia.com I'd think it wasn't that scalable at all. I mean there are sites with higher load using a tenth of the hardware that Macromedia.com uses. -Matt ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
