[cfaussie] Re: onApplicationStart() running more than once
Is onapplicationstart returning true? If it doesn't return true then it will continue to execute as you've described. Then again.. I could be wrong :) On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thanks for your quick reply Andrew. I am unsure of how these certain conditions are not met? I have only written code in the onApplicationStart() and no where else, yet. Also, there are no changes to the appname. Thanks, On Apr 22, 10:33 pm, Andrew Scott [EMAIL PROTECTED] wrote: Actually, onApplicationStart will run each and everytime when certain conditions are not met. So these conditions can be things like, session identifier being corrupt or changing. Application name corrupt or changing. I would more than likely begin looking at the fact that you are expiring your session identifiers, and a certain user has cookies for that site blocked / disabled first. Then maybe look at the session identifier to see if it is being changed while passing it back to the server. Last but not least if all else fails then the application name must be changing under certain conditions. Andrew Scott Senior Coldfusion Developer Aegeon Pty. Ltd.www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 -Original Message- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, 23 April 2007 10:22 AM To: cfaussie Subject: [cfaussie] onApplicationStart() running more than once Hey guys, I am writing a new application.cfc for a site. I set up and store all the data required for our application to run in the onApplicationStart() . Now i have run into an issue. The onApplicationStart() function runs on each page load. This is weird considering it should only run once on start up. Any ideas why this occurs? Thanks, --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Request VS Application Scope
Hi all, I was wondering what the differences between the request and application variables are. I use the application variable to store the variables that dont change much (dsn, page info, page content etc...). Now i dont seem to understand the request scope and its uses well enough to use them. Can anyone shed some light on this topic for me. i have read some articles on the net, but they dont seem to explain the concept well enough. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Request VS Application Scope
Hi all, I was wondering what the differences between the request and application variables are. I use the application variable to store the variables that dont change much (dsn, page info, page content etc...). Now i dont seem to understand the request scope and its uses well enough to use them. Can anyone shed some light on this topic for me. i have read some articles on the net, but they dont seem to explain the concept well enough. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Request scope variables only exist for the duration of a page request. They don't consume RAM like Application variables do. And are ideal for what you are using Application vars for. Best defined in Application.cfm as it is executed before all other templates: eg: cfsilent cfapplication name=MyApp_WWW_23APR2007 setclientcookies=yes setdomaincookies=yes sessionmanagement=Yes clientmanagement=yes clientstorage=cookie cfparam name=Request.DataSourceName default=MyApp cfparam name=Request.DatabaseTablePrefix default=MyApp cfparam name=Request.ApplicationTitle default=MyApp cfparam name=Request.CopyrightYear default=#DateFormat(Now(), )# cfparam name=Request.FlashFormSkin default=haloblue cfparam name=Request.FlashFormSkinInterior default=haloorange cfparam name=Request.FlashFormSkinExterior default=halogreen cfparam name=Request.FlashFormBackgroundColour default=background-color:##ff; cfset Request.NewLocale = SetLocale(EN_AU) cfinclude template=inc_custom_functions.cfm /cfsilent --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Would it be better to have these variables in the application scope over the request scope as they should exist for the entire application rather than single page request? This beginning to confuse me even more On Apr 23, 6:53 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: Request scope variables only exist for the duration of a page request. They don't consume RAM like Application variables do. And are ideal for what you are using Application vars for. Best defined in Application.cfm as it is executed before all other templates: eg: cfsilent cfapplication name=MyApp_WWW_23APR2007 setclientcookies=yes setdomaincookies=yes sessionmanagement=Yes clientmanagement=yes clientstorage=cookie cfparam name=Request.DataSourceName default=MyApp cfparam name=Request.DatabaseTablePrefix default=MyApp cfparam name=Request.ApplicationTitle default=MyApp cfparam name=Request.CopyrightYear default=#DateFormat(Now(), )# cfparam name=Request.FlashFormSkin default=haloblue cfparam name=Request.FlashFormSkinInterior default=haloorange cfparam name=Request.FlashFormSkinExterior default=halogreen cfparam name=Request.FlashFormBackgroundColour default=background-color:##ff; cfset Request.NewLocale = SetLocale(EN_AU) cfinclude template=inc_custom_functions.cfm /cfsilent --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/ http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Yeah thanks for that. So basically, when would you need to be using the request scope? I use the application.cfc so i would have all this in my onrequeststart(). Thanks once again guys, On Apr 23, 7:41 pm, M@ Bourke [EMAIL PROTECTED] wrote: I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
So basically, when would you need to be using the request scope? you never need to use much of anything, it's when might you use the request scope I personally will load querys and stuff into it, that is going to be accessed for just the page request and be accessed by any files throughout the request. M@ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
I agree with M@, things that are going to be constant and apply across the board to the entire application I would stick in the Application scope. Why the hell Peter does this in the request scope is beyond reasoning to me. There is very little need to use the request scope, unless you want a way to make variables global to all functions, templates. I'll throw the session scope at you as well, which you can use for the life of a users session that is not applicable to other users of that application. On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yeah thanks for that. So basically, when would you need to be using the request scope? I use the application.cfc so i would have all this in my onrequeststart(). Thanks once again guys, On Apr 23, 7:41 pm, M@ Bourke [EMAIL PROTECTED] wrote: I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Dude, to answer you original question, which is what the hell is the request scope? (if I understand you well): the request scope gives you access to the whole HTTP request entity. So you can see it as one round-trip to the server. If inside a template, you have a cfmodule, or a cf_whatever, a variable defined as request.var1, will be visible, whereas a non scoped variable (or really, a variables. variable) is only visible within a given template, and the templates it includes (as in cfinclude). tof On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yeah thanks for that. So basically, when would you need to be using the request scope? I use the application.cfc so i would have all this in my onrequeststart(). Thanks once again guys, On Apr 23, 7:41 pm, M@ Bourke [EMAIL PROTECTED] wrote: I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Actually that is not true... All variables in all scopes are accessible in every aspect of coldfusion, with excpetion to limitations to CFX tags. On 4/23/07, christophe albrech [EMAIL PROTECTED] wrote: Dude, to answer you original question, which is what the hell is the request scope? (if I understand you well): the request scope gives you access to the whole HTTP request entity. So you can see it as one round-trip to the server. If inside a template, you have a cfmodule, or a cf_whatever, a variable defined as request.var1, will be visible, whereas a non scoped variable (or really, a variables. variable) is only visible within a given template, and the templates it includes (as in cfinclude). tof On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yeah thanks for that. So basically, when would you need to be using the request scope? I use the application.cfc so i would have all this in my onrequeststart(). Thanks once again guys, On Apr 23, 7:41 pm, M@ Bourke [EMAIL PROTECTED] wrote: I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
as I understand it, the VARIABLES scope is only available to the current template if you don't specify a scope, it ends up in the VARIABLES scope. I think the THIS scope for CFCs is limited to the CFC On 4/23/07, Andrew Scott [EMAIL PROTECTED] wrote: Actually that is not true... All variables in all scopes are accessible in every aspect of coldfusion, with excpetion to limitations to CFX tags. On 4/23/07, christophe albrech [EMAIL PROTECTED] wrote: Dude, to answer you original question, which is what the hell is the request scope? (if I understand you well): the request scope gives you access to the whole HTTP request entity. So you can see it as one round-trip to the server. If inside a template, you have a cfmodule, or a cf_whatever, a variable defined as request.var1, will be visible, whereas a non scoped variable (or really, a variables. variable) is only visible within a given template, and the templates it includes (as in cfinclude). tof On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yeah thanks for that. So basically, when would you need to be using the request scope? I use the application.cfc so i would have all this in my onrequeststart(). Thanks once again guys, On Apr 23, 7:41 pm, M@ Bourke [EMAIL PROTECTED] wrote: I'd either put it in your application scope or cache ya query. if it's going to be available for every user all the time then application shouldn't be a problem if the site's busy and ya setting it to request each page request for each user then it would be using a lot of memory although the memory would be getting cleaned up it would be continually getting filled up. I'm not an expert on the inner workings of the cf server but I'd try the application scope and if you don't get any issues with it then for this case just sick with it. M@ On 4/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well i store them in the application scope because i call some function to fetch page information from the database and i wouldnt want them to load on every page request, I would much rather store them in the app scope and call them from the pages This was implemented to avoid hitting the db all the time for fetch page elements and things like that. If i was to place them in the request scope would this mean they would load on every page request? Obs this isnt what i would want. On Apr 23, 7:23 pm, Peter Tilbrook [EMAIL PROTECTED] wrote: No point. In fact an unnecessary overhead. Once the request is finished they are no longer required. Another page request - they are used - then zip. No locking or anything required. Application vars have their place but for - at least how I use them - like datasourcenames and such - Request scope is perfectly suitable. Just declare them in the Application.cfm so they are available to all page requests. -- Peter Tilbrook ColdGen Internet Solutions President, ACT and Region ColdFusion Users Group PO Box 2247 Queanbeyan, NSW, 2620 AUSTRALIA http://www.coldgen.com/http://www.actcfug.com/ Tel: +61-2-6284-2727 Mob: +61-0432-897-437 Email: [EMAIL PROTECTED] MSN Messenger Live: Desktop General Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 -- If you are not living on the edge, You are taking up too much space. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: [Ann Syd] Why Eclipse and Using Flex 2 instead of Coldfusion Flash Forms
Monday 30th April, the Sydney Flash Platform Developers Group is meeting with the following topics:- 1.) With Flex Builder and CFEclipse based on the free open source Eclipse IDE, we'll walk though the features of Eclipse to understand why. 2.) Currently Coldfusion's Flash forms are based on Flex 1.5. Tonight, Andrew Muller will show use how to Flex 2 instead. 3.) A round of all latest delevelopments since the last user group meeting. When: 5:00pm for 5:30pm start and finishing at approximately 8 pm. Where: Adobe's Office's in Chatswood (for directions see http://maps.google.com/maps/ms?ie=UTF8msa=0hl=enmsid=103768339359859737595.01121464ab70d5fde) Please register your RSVP at http://sydneyflashdevelopers.eventbrite.com/ Note: the building is locked at 6pm. Chris -- Chris Velevitch Manager - Sydney Flash Platform Developers Group m: 0415 469 095 www.flashdev.org.au --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
The THIS scope is also accessible by the calling page. the var (whats the name of this scope/thingo?) is accessible by only the current cfc cfset var crud = chuck some crud on it On 4/23/07, AJ Mercer [EMAIL PROTECTED] wrote: as I understand it, the VARIABLES scope is only available to the current template if you don't specify a scope, it ends up in the VARIABLES scope. I think the THIS scope for CFCs is limited to the CFC --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
M@ you meant function.. Variables scope is what you meant for CFC's... On 4/23/07, M@ Bourke [EMAIL PROTECTED] wrote: The THIS scope is also accessible by the calling page. the var (whats the name of this scope/thingo?) is accessible by only the current cfc cfset var crud = chuck some crud on it On 4/23/07, AJ Mercer [EMAIL PROTECTED] wrote: as I understand it, the VARIABLES scope is only available to the current template if you don't specify a scope, it ends up in the VARIABLES scope. I think the THIS scope for CFCs is limited to the CFC -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
Request scope is less important now that it used to be. In the days up to CF5.2, locking was a huge issue whenever you tried to read the application scope so it was a matter of routine that for each page request, you copied all the applicatoin variables into the request scope and used them throughout your pages rather than application variables. Since MX, locking is less of an issue and it's ok to read application variables without having to lock first in most circumstances. Therefore there's less need to use the request scope. Once, in the dim distant pastI used to use request variables everywhere. Nowdays i hardly use them at all. But if you do use request variables, there's nothing wrong with that. Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Re: Request VS Application Scope
The important thing to realise is how long each of these scopes last, and where they can be seen. Server scope is available to every page on the server, regardless of application name specified. Their timeout is defined in your Cf administrator, and typically last for a few days. Put things in here that are relevant to every application application and not to specific applications or users. This scope is empty for the first user of the server, or if no one has visited the server for the specified timeout period. Application scope is available to every page that shares the same application name in your cfapplication tag. Their timeout is defined in your Cf administrator, and typically last for a few days. Put things in here that are relevant to the entire application and not to specific users. This scope is empty for the first user of the application, or if no one has visited the application for the specified timeout period. Session scope is available to every page that one user calls in their session within one app. Their timeout is defined in your Cf administrator, and typically last for a few hours, or when the user's session timesout. Put things in here that are relevant to the user's session and not to just one page. This scope is empty for the each user when they start a new session, or if they allow their session to timeout. Request scope is available to every part of a single page request. This scope is created when a page load is started and is lost when the page finishes loading. Put things in here that are relevant to just this page, where you want something to be available to several sections of the same page. This scope is empty at the beginning of each and every page, and is cleared at the end of each and every page. Its important to remember to check for whether these variables have timed out or not, for all cases except for request. Generally, I'd set a bunch of them in a logical group, high up in the Application.cfm (or similar) and surround them with a condition that tests for the existance (isdefined) of one of the variables in the group (because if one timesout, they'll all timeout). That way they only get set if they don't exist, but they will always be set if the don't exist. And as Andrew was saying, back in the day, I'd have great herds of values in the Application scope and then move them at the beginning of every page into the request scope, so that I only had to lock the application scope when this copy was done. In these enlightened days, this is not necessary (under normal conditions). Hope that helps. Darren Tracey CFUG QLD Manager Australia On Apr 23, 6:43 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi all, I was wondering what the differences between the request and application variables are. I use the application variable to store the variables that dont change much (dsn, page info, page content etc...). Now i dont seem to understand the request scope and its uses well enough to use them. Can anyone shed some light on this topic for me. i have read some articles on the net, but they dont seem to explain the concept well enough. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] CFMX 7 New Install - Error Occurred While Processing Request
Hi, new install of cf mx 7 on a new DELL PC. getting the above error when attempting to browse http://localhost/CFIDE/administrator/index.cfm IIS is started. CF services are started. I have run the IIS_connector.bat in the bin\connector directory. rebooted a couple of times. The IIS website is working. Application log says: Severity,ThreadID,Date,Time,Application,Message Information,jrpp-3,04/24/07,15:08:36,,C:\CFusionMX\logs\application.log initialized Error,jrpp-3,04/24/07,15:08:36,,null The specific seruence of files included or processed is: null Error,jrpp-3,04/24/07,15:13:28,,null The specific seruence of files included or processed is: null Exception Log: Error,jrpp-3,04/24/07,15:13:28,,null The specific seruence of files included or processed is: null java.lang.NoClassDefFoundError at javax.crypto.Cipher.getInstance([DashoPro-V1.2-120198]) at coldfusion.compiler.TemplateReader.decrypt(Unknown Source) at coldfusion.compiler.TemplateReader.init(Unknown Source) at coldfusion.compiler.NeoTranslationContext.getPageReader(Unknown Source) at coldfusion.compiler.NeoTranslator.translateJava(Unknown Source) at coldfusion.compiler.NeoTranslator.translateJava(Unknown Source) at coldfusion.runtime.TemplateClassLoader$1.fetch(Unknown Source) at coldfusion.util.LruCache.get(Unknown Source) at coldfusion.runtime.TemplateClassLoader$TemplateCache.fetchSerial(Unknown Source) at coldfusion.util.AbstractCache.fetch(Unknown Source) at coldfusion.util.SoftCache.get(Unknown Source) at coldfusion.runtime.TemplateClassLoader.findClass(Unknown Source) at coldfusion.filter.PathFilter.invoke(Unknown Source) at coldfusion.filter.ExceptionFilter.invoke(Unknown Source) at coldfusion.filter.ClientScopePersistenceFilter.invoke(Unknown Source) at coldfusion.filter.BrowserFilter.invoke(Unknown Source) at coldfusion.filter.GlobalsFilter.invoke(Unknown Source) at coldfusion.filter.DatasourceFilter.invoke(Unknown Source) at coldfusion.CfmServlet.service(Unknown Source) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunReruestDispatcher.invoke(JRunReruestDispatcher.java:241) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527) at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:198) at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:348) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:451) at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:294) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Any suggestions? trying to check adobe website now.. running slw. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
[cfaussie] Commercial data list of aus suburbs postcodes etc
Hey all Anyone know of a commercial provider of a list or preferably a web service where we can get a list of all suburbs matching a postcode? Dont need GPS co-ordinates. Cheers Jason Jason Bayly Senior Developer d: (02) 9274 8061 p: (02) 9274 8000 f: (02) 9274 8099 m: 0425 222 325 w: www.newgency.comNewgency Pty Ltd Web | Multimedia | eMarketing Address: 224 Riley Street Surry Hills, NSW 2010 Sydney, Australia --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~--~~~~--~~--~--~---
