This is a repost as I didn't notice any answers and I had to switch mail accounts (Hotmail keep dumping the digest into the Junk Mail folder, and my alternate account keeps going into dev/null! )
FB newbie have several questions about FB3... I've read all the presentations on fusebox.org. I actually got applications WORKING but I can't find answers to these questions. 1) In a "login" module, there are cases where you need to look at a query and decide where to branch to. Is that considered a query module or an action module? 2) What is the "better" way to maintain session when using CFLOCATION? Should I use the custom tag CF_LOCATION instead? I see a lot of code in samples (like the TaskManager I got from Fusium) that uses BOTH... If success, CF_LOCATION is used to continue (I presume to keep the CFID/CFTOKEN cookies?) and if failed CFLOCATION is used to jump to "login failed" page. Did I understand that correctly? What are the implications of using the wrong one? 3) I was reading the CFDJ on those articles about maintaining sessions and how to prevent session hijacking and all that. I am working on an app that deal with some financial information and need session and security. I found the "Fusebox Security Model" sample app (the one from onshop.com) but I don't need multilevel security in this case. Is there a simpler session/access app available for reference? 4) How DOES one handle session timeouts in terms of fusebox? Should there be a fuseaction about session timeout? 5) I also read in CFDJ about that CF_REQUEST tag which makes ANY request scope variable into session or client scope and vice versa. It sounds good, but it seems to have some problems as fusebox uses a LOT of request scope structures and such. Does that work with Fusebox at all? What are the implications? 6) There are some cases where a "fixed entry and exit" point is not desirable. For example, if I called screen A from screen B, I would want screen A to return to screen B. Yet if I called screen A from screen C, I would want to return to C. How do you handle that in FB3? It seems that XFA is pretty "fixed" when it comes to the 'return' paths. In a wireframe, you need to code two or three separate exit pts to reflect situations like this. Right now I'm passing a URL scope variable called OFA (original fuseaction) but I'm not sure if that's the "right" solution. I have more questions but those can wait. :-) --remove NOSPAMYOUIDIOT to reply, [EMAIL PROTECTED] is invalid-- K S C H A N G (AT) PC Guru, web developer, gamer, Trekker E X C I T E (DOT) COM database developer, idea man, IT guy --If it looks too obvious, it probably is. -- anonymous ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
