True, I hadn't thought of that. If I wish to drag my circuit to another application then it will fail because of the globals being missing.
This is why I asked the question in the first place. Thanks for your valuable input I will rethink my strategy. Although I am currently wondering if there will ever be a perfect solution or just a best compromise. Regards Ellis -----Original Message----- From: Paul Johnston [mailto:[EMAIL PROTECTED] Sent: 24 October 2003 10:00 To: [EMAIL PROTECTED] > Right. The concensus is then, that we have a globals > directory. That is the way I have been going anyway but just > wanted to check out the combined brain power of this list I would suggest that this isn't a good idea. The whole point of fusebox is that you can effectively "drag and drop" different circuits into applications, so you end up with a login circuit and an admin circuit and a... Etc. This means that if there are includes duplicated within the other circuits, you can use the fuse you have it already in and use an API call (Custom Tag). Iow: circuits: login, main, admin, news, articles In news, you want to find out if the user is logged in and show links to "premium" content or something, so instead of creating a separate qry file or anything in the news circuit, you create a login fuse to do the job and call via a CT: <cfmodule template="...whatever the request.self is..." checkloggedin="#session.user#" etc...> Or something like that. Although alternatively (another way I've done it before) is to create a Custom Function in a circuit that gets created and stored in the session scope (or wherever) to allow access to the information in another circuit. Basically, what you don't want to do is duplicate code. If you do, it's poor design, and not poor coding. Poor coding is when it doesn't work! Paul -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
