best practice for CFCDynamicProxy -- one for each proxied type? or one for the entire app?

[Marc Esher]

All,

I'm creating several different kinds of proxies via CFCDynamicProxy:

CFCDynamicProxy =
application.javaloader.create("com.compoundtheory.coldfusion.cfc.CFCDynamicProxy");

And then using CFCDynamicProxy.createInstance(...);

My question is: is there any reason why I *wouldn't* want to create
that as an app-scoped object, and use that singleton instance to
create all my proxy objects?

Or is it intended to have a 1:1 between the CFCDP object and the
proxied objects being created?

Thanks.

Marc

[Mark Mandel]

I can't think of any reason at all to not have it as a singleton.

AS you can see from the code - createInstance is static, and creates a new instance of the CFCDynamicProxy on each invocation.

https://github.com/markmandel/JavaLoader/blob/develop/java/cfcdynamicproxy/src/com/compoundtheory/coldfusion/cfc/CFCDynamicProxy.java#L133

Mark

On Wed, Jan 18, 2012 at 10:34 PM, Marc Esher <marc....@gmail.com> wrote:

My question is: is there any reason why I *wouldn't* want to create
that as an app-scoped object, and use that singleton instance to
create all my proxy objects?

--
E: mark....@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

2 Devs from Down Under Podcast

http://www.2ddu.com/

[Marc Esher]

Thanks Mark. I looked at the code, and that's why I asked... that
"backupFusionContext" class variable had me worried since it looks
like it could *possibly* be used during proxy invocation.

[Mark Mandel]

Yeah, it's used when we need a context and we're not on a ColdFusion request - so err just use the one from when the proxy was generated.

Mark

Sent from my mobile doohickey.

[Marc Esher]

excellent. thanks!