--
You received this message because you are subscribed to the Google Groups "ColdSpring-Users" group.
To post to this group, send email to coldspri...@googlegroups.com.
To unsubscribe from this group, send email to coldspring-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/coldspring-users?hl=en.
If you are doing caching across clusters, you should really look.at a clustered cache like EhCache or memcache for your needs.
Really, your issue is that the application scope is per server, which is not a coldspring issue per se, but just how cf applications are architected.
Sent from my mobile device
On 4 Jun 2010 20:15, "Klaas-Jan Winkel" <k.wi...@gmail.com> wrote:
oops.. so maybe i should not worry to much about this caching.
On Fri, Jun 4, 2010 at 12:14 PM, Klaas-Jan Winkel <k.wi...@gmail.com> wrote:
>
> Ow yeah, all the...
--
That's the root of your problem.
If you put ColdSpring in application scope, your singletons will be
per-server by definition.
The solution is to use a distributed (shared) cache on your cluster
and put the ColdSpring instance in that (assuming you can find one
that will be able to replicate CFML objects correctly) or put your
singletons directly into that cache (probably easier).
That's just a basic ColdFusion architecture issue: scopes are not
shared across servers.
FWIW, Railo supports distributed caches for objects, templates,
queries and the ram:// VFS.
--
Sean A Corfield -- (904) 302-SEAN
Railo Technologies, Inc. -- http://getrailo.com/
An Architect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood