I am in the process of re-writing several of those areas into Mach II and have a question on passing in our "userData" into the CFC. Once a user is logged in, we create a structure of all his details (id, name, etc) and store it in a client variable as a wddx object. The call to get the client.userData and deserialize it is in the header.cfm. The structure of the new Mach II code will be:
header.cfm
machII.cfm (yes all events)
footer.cfm
How are these files related? Do you have page.cfm which has three <cfinclude>s?
If header.cfm already deserializes client.userData, I'd have it put the result in request scope and access it that way within the Mach II (request.userData). It's kinda like a Band-Aid on a wart tho' but probably the least intrusive way to handle this until you can rewrite the entire app.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
