I read in posts that the "object" does not replicate to another clustered
server, just the data structure. (Or is this fixed with 6.1 ... did I
misunderstand the post?)
CFCs do not serialize so JRun cannot automatically replicate them when it replicates other session data. As I pointed out, session replication is a tradeoff: it introduces network overhead and some performance degradation for 24x7 session availability in a cluster. I wouldn't consider it a 'usual' setup since most websites do not need that level of availability (macromedia.com does not use session replication, for example).
However, you can easily detect that you are the recipient of a failed replication:
<cfif structKeyExists(session,"myobj") and
not isObject(session.myobj)>
<!--- need to recreate session.myobj --->
</cfif>So you have you design your system to use CFCs in session scope only in ways that you can recreate them if needed. For example, you might cache a shopping cart object in session scope but write all changes to a database - the in-session CFC being merely an optimization - so it is easy to recreate it if you lose the in-session CFC (this is essentially what macromedia.com does on its European online stores to allow for a persistent shopping cart, i.e., your cart is still around the next day or so if you decide not to complete a purchase - quite a few e-commerce sites do that).
The other thing to bear in mind is that session replication only shares session scope across server instances, server scope and application scope are always per-instance and never shared. If you need to 'replicate' information across instances for server / application scope, you need to come up with your own machinery for that (again, something that macromedia.com actually does through a variety of methods...).
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
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).
