I have been using CFIMPORT heavily of late and had no problems, though I
have not done any heavy load testing around that issue (but since it's a
compile-time issue I very much doubt there are any real performance
implications).
The one issue I've run into is that since CFIMPORT cannot be loaded with a
dynamic path you end up potentially have issues if you want to reorganize
your code base. This is really a minor problem, especially since a global
find/replace would take care of it in most cases.
I wish you could import CFC packages as well, perhaps with syntax like:
createObject("component","prefix:component");
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Robby L.
> Sent: Tuesday, July 22, 2003 10:51 AM
> To: [EMAIL PROTECTED]
> Subject: [CFCDev] general thoughts on cfimport?
>
>
> I know this isn't heavily related to cfcs, but I thought I would
> ask to get
> the general vibe.
>
> My latest application is heavily based on cfimport. I'm using it
> for general
> ui, display, forms, etc but I wanted to see if there was any
> heavy downside
> to it that would cause concern, now or down the road.
>
> Just trying to see if there is something out of hindsight that will cause
> headaches tomorrow.
>
> Cheers
> Robby
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
