not to doubt you, but I find it odd that this bug hasn't shown itself anywhere else in CFMX-land. I also haven't seen it documented anywhere. I know that cffile is not thread safe within a persistant CFC, but that's still not the problem at hand. Also, the error, according to Jrun, is that the http request itself was malformed (hence the 500).
-Dave >>> [EMAIL PROTECTED] 8/9/2004 8:53:45 AM >>> I believe the "error" was due to some quirkiness in CFMX that occurred intermittently when the CFFILE tag was encapsulated inside a component. The fix was to call the CFFILE tag directly. For this or any other fix all you need to do is DIFF the versions of the relevant file code causing you problems with a CVS diffing tool. That may sound a little unhelpful, but truly its worth the effort to get to grips with how these things work. If you are working in an environment like CFECLIPSE this is simplicity itself. I might also add that v2.2 milestone is very stable. In fact I'm finding the v2.3 alpha very stable for that matter. --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
