Sean and Barry,
thanks for your input on this issue. Let me put my question in
perspective. I use a resource bundle manager that keeps all of the
bundle instances in the application scope. The bundles are persisted
to file when an update is made, so I thought the easiest thing to do
would be to re-initialise the bundles when any updates are made. I do
this by passing the variable 'initCluster' in through a cfhttp post.
i.e.
<!--- initialise rbMan --->
<cfif NOT IsDefined("application.rbMan") OR isDefined("attributes.reInit")>
<cfset application.rbMan = CreateObject('component', 'org.rbMan.rbMan') />
<cfset results = application.rbMan.init(request.bundleDir) />
</cfif>
<!--- re-initialise the cluster --->
<cfif isDefined("attributes.initCluster")>
<!--- reInit each cluster instance --->
<cfhttp method="post" url="http://203.57.82.204:8100/index.cfm"; timeout="30">
<cfhttpparam name = "fusebox.load" type = "FormField" value = "true">
<cfhttpparam name = "reinit" type = "FormField" value = "yes">
</cfhttp>
<cfhttp method="post" url="http://203.57.82.203:8100/index.cfm"; timeout="30">
<cfhttpparam name = "fusebox.load" type = "FormField" value = "true">
<cfhttpparam name = "reinit" type = "FormField" value = "yes">
</cfhttp>
</cfif>
I agree that you'd want to keep most info in the database, but in this
case I think the benifits of keeping the bundles in memory outweighs
the overhead involved in re-initialising every now and then. This only
happens occasionally so it won't stress the server too much.
Using a webservice would give you more precise control over what you
want to re-initialise. I might have a closer look at using a
webservice to re-init the individual bundles.
--
Jason Sheedy
www.jmpj.net
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
