On Apr 6, 2005 10:24 PM, dcooper @ macromedia. com dcooper @ macromedia. com <[EMAIL PROTECTED]> wrote: > Client variables work GREAT with CFMX7 Gateways. All good, no worries. No > cookies (obviously), but we made sure they work in the context of Gateway > apps, as with session variables.
Since client variables rely on a cookie to identify a user, could you clarify how that works with event gateways since they don't have cookies? Presumably if an asynch CFML gateway CFC wants to access the same client scope variables that the originally requested page can access, some magic has to be done so that the event gateway knows how to access the same client variables? > I believe the error Tony was getting was because he was he was running in > Developer Edition mode, which enforces limits on the number of Event Gateway > requests, threads and originator ID's. Evaluation mode and Enterprise > Edition obviously don't have these restrictions. So he got a database deadlock on client storage because of that? -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201823 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
