----- Original Message ----- 
From: "Matthew Williams" <[EMAIL PROTECTED]>


> Uh, what?  Session replication has been working for me starting with MX
> 6.1 and continues to work fine now that we've moved to CF8.

How do you define "working"?  When you can't place CFCs or XML objects in 
your session scope without ugly erros, I don't call that working. 
Serialization of complex objects has plauged session replication for a 
while.  CF8 made CFCs serializable and that was very good, but to this day 
(and to my knowledge), ColdFusion is still incapable of serializing complex 
variables (Arrays, Dates, Query objects) within a CFC. (Adobe Bug #70580)
I know there are people who use session replciation, but in general, my 
perception (from this list anyway) is that a lot of people have simply 
enabled sticky sessions and then clocked out.

I've also
> not had an issue with cfchart since the information replicates within
> the cluster.

I'm not sure what you speak of, but to my knowledge this is not operation 
out of the box since cfchart's cache location defaults to a local directory. 
(Which is why it qualifies in my gotcha catagory) Your options are to cache 
to a shared network location, or enable some sort of file replication beween 
your chart caching folders.  Keep in mind, I didn't say it was impossible. 
I simply said it was a gotcha.
To my knowledge, cfimage does not allow customization of the caching folder.

  And, as an added bonus, the latest JRun updater for CF8
> brings us partial session updates!

Your are right.  This is a very good thing.

~Brad 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:311827
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to