> application.cfm:
>
> <cflock timeout="20" throwontimeout="yes" name="activeXinterface"
> type="EXCLUSIVE">
> <cfif not isdefined("server.interkomobject")>
> <cfobject type="COM" name="server.interkomobject"
> class="InterKOMConnector.IKConnector" action="create" context="LOCAL">
> </cfif>
> </cflock>
>
>
> getinfo.cfm:
>
> <cflock timeout="20" throwontimeout="yes" name="activeXinterface"
> type="EXCLUSIVE">
> <cfset session.connectorresult=
> server.interkomobject.processandparserequests(session.cmdstring)>
> </cflock>
In general, I wouldn't recommend storing COM objects within persistent
variables - that doesn't even work well in ASP!
That being said, it's my understanding that CF 5 changed some of the details
about how COM objects stored in persistent memory variables will perform. I
don't really know the details; the release notes basically said "it should
work better than before", but no real internal details were provided, if I
recall correctly.
What you might try doing, for diagnostic purposes, is changing your code so
that you're not using persistent memory scopes, and see if that works. For
example, instantiate the object as a local variable, and use a local
variable for the argument and the returned value.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
______________________________________________________________________
Why Share?
Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
Instant Activation � $99/Month � Free Setup
http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
