None that I can think of, but given your choice, use cfinvoke or not, I think it’s a moot point J

 

Marlon

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vidar Einlien
Sent: Wednesday, July 07, 2004 12:55 AM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] CFOBJECT and shared hosting

 

> If you need to use CFInvoke, you could create an init method that would return “this”.  This would roughly emulate CFObject/CreateObject.

 

This is what I have done, I like to use the createObject method but since this application will be used by different people on shared hosting, I guess I should use the cfinvoke to be on the safe side. Are there any other issues I need be aware when using cfinvoke instead of createObject performance vice etc.

 

cheers

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vidar Einlien
Sent: Tuesday, July 06, 2004 11:15 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] CFOBJECT and shared hosting

 

Anyone? Please :)

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vidar Einlien
Sent: Tuesday, 06 July, 2004 16:29
To: [EMAIL PROTECTED]
Subject: [CFCDev] CFOBJECT and shared hosting

 

Hi all, I just have a quick question about the CFOBJECT and shared hosting.

Usually on shared hosting the CFOBJECT tag is disabled and my question is: Is using CFOBJECT to create an instance of a component the same as setting <cfset q = createObject("component", "some Component ") />, so if CFOBJECT is disabled I cant use the <cfset> method?

 

And what is the difference in using the createobject method compared to use the <cfinvoke> method?

 

cheers

Reply via email to