I'm thinking, David. We encountered pcode errors quite often before we began
locking reads and writes to application and session-scoped variables. I'm
not sure we locked all reads and writes. There may have been a few
stragglers, because we did get the occasional pcode error once and a while.
We never did track it down. gaISA had issues too.
---
Jeffrey B. Marsh
Professionals built the Titanic.
Amateurs built the Ark.
CF5, huh? We didn't have much trouble doing it with CF4.01, did we? What
changed? Jeff, back me up here...
David Huyck
[EMAIL PROTECTED]
| $5 to be delivered at the next major CF conference, should I be able to
| reproduce the error on my machine (single proc p3-650, 256 mb ram, CF 5
Beta
| 3, PWS, NT 4 Workstation SP6). The cash only goes to the first person...
****************************************************************************
This message is intended for the sole use of the individual and entity to
which it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose or
distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message. Thank you very
much.
****************************************************************************
****************************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
