Because each of our customer's data is stored on separate DSNs, and the if the DSN string is passed into an object on load as described in the, it stays there until Mach-II is reloaded. This can cause customer 1 to read data from customer 2 if Mach-II is not reloaded between customer 1's log out and customer 2's login. My solution was to initialize the referenced objects before the function call, so that they would collect the new dsn value from a new login instead of the cached dsn value.
On Nov 7, 2:16 pm, Matthew Woodward <[email protected]> wrote: > On Mon, Nov 7, 2011 at 11:11 AM, RobM <[email protected]> wrote: > > Hello, > > I'm working on making our existing Mach-ii application initialize the > > objects it needs when it calls a function in the listener as opposed > > to initializing them on load. > > Why? > -- > Matthew Woodward > [email protected]http://blog.mattwoodward.com > identi.ca / Twitter: @mpwoodward > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments.http://www.gnu.org/philosophy/no-word-attachments.html -- To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
