Sean Corfield posted a link on his blog to a Macromedia technote which warns
for the use of client variables in combination with asynchronous requests from
the same client.
The comments turned into a nice technical discussion about the use of cfc's
stored in a persistent scope and the use in a clustered environment.
The macromedia documentation states:
"You cannot cluster session-based persistent ColdFusion Components. You cannot
store ColdFusion components in the session scope when using clustering and
session failover. Currently ColdFusion MX does not support serialization of
CFCs; therefore, you cannot replicate their state across a ColdFusion MX
cluster. The following code demonstrates storing an instance of a components in
the session scope. "
With a simple example of what cannot be done in a clustered environment:
<cfset session.securitycomp=CreateObject("component","directory.componentname")>
With the ability of CFC's since CFMX, and so, storing complex data into a
persistent scope, how do other users with extensive use of CFC's in persistent
scope handle this?
I've read somewhere the Macromedia stores CFC's in the server scope, but I can
imagine the website doesn't run on a single server. How do they manage this?
Maybe Macromedia also reads this, are there plans to support clustered complete
data in future?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:191864
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
