[ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-10-24 Thread Ajas Mohammed
Hi,

Just wondering if anyone can share there Development vs Production
Application.cfm or .cfc techniques. If you have a sample application.cfm or
.cfc file to share, then that would be great.

I will give some background as to how I am doing this right now. I usually
set application variables which of course, have different values in
development vs production. Best example is pathtoSomething application
variable's value which would be different in development and production.

Any other advices are also welcome.

Thanks,

Ajas Mohammed.


RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-10-24 Thread Wes Byrd
I like to keep the application.cfc the same and use an XML file to store the 
application variables and their values that differ on each machine.  So, in the 
application.cfc on application start, you can execute a component that can 
parse the XML and set application scope vars accordingly.

Wes

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed
Sent: Saturday, October 24, 2009 3:53 PM
To: discussion@acfug.org
Subject: [ACFUG Discuss] Development vs Production Application.cfm and other 
things...

Hi,

Just wondering if anyone can share there Development vs Production 
Application.cfm or .cfc techniques. If you have a sample application.cfm or 
.cfc file to share, then that would be great.

I will give some background as to how I am doing this right now. I usually set 
application variables which of course, have different values in development 
vs production. Best example is pathtoSomething application variable's value 
which would be different in development and production.

Any other advices are also welcome.

Thanks,

Ajas Mohammed.





-

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-




RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-10-24 Thread Charlie Arehart
Or on may find it a little easier to use ini files, and CF's functions to
read them (added in CF 6), such as getprofilestring, getprofilesections,
setprofilestring.

 

/charlie

 

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Wes Byrd
Sent: Saturday, October 24, 2009 6:03 PM
To: discussion@acfug.org
Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and
other things...

 

I like to keep the application.cfc the same and use an XML file to store the
application variables and their values that differ on each machine.  So, in
the application.cfc on application start, you can execute a component that
can parse the XML and set application scope vars accordingly.

 

Wes

 

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed
Sent: Saturday, October 24, 2009 3:53 PM
To: discussion@acfug.org
Subject: [ACFUG Discuss] Development vs Production Application.cfm and other
things...

 

Hi,

 

Just wondering if anyone can share there Development vs Production
Application.cfm or .cfc techniques. If you have a sample application.cfm or
.cfc file to share, then that would be great.  

 

I will give some background as to how I am doing this right now. I usually
set application variables which of course, have different values in
development vs production. Best example is pathtoSomething application
variable's value which would be different in development and production.

 

Any other advices are also welcome.

 

Thanks,

 

Ajas Mohammed.

 

 


- 
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform 

For more info, see http://www.acfug.org/mailinglists 
Archive @ http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by FusionLink <http://www.fusionlink.com>  
- 




-
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-



Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-10-29 Thread Jim Rising
I've been using Coldbox lately and have been making use of the environment
control interceptors:

http://ortus.svnrepository.com/coldbox/trac.cgi/wiki/cbEnvironmentControl

Previously I had built what essentially amounted to the same idea by pulling
in environment specific settings via xml onApplicationStart() and using a
naming convention for the files based on cgi.remote_host and host headers
setup within apache or IIS. if the browser is looking at
http://dev.mydomain.com ... app.cfc pulled in '/environments/dev_mydomain_
com.xml'.

-- 
Jim Rising
Serial Entrepreneur
Software Engineer
Web Developer

"Knowledge work requires both autonomy and accountability."

On Sat, Oct 24, 2009 at 2:53 PM, Ajas Mohammed  wrote:

> Hi,
>
> Just wondering if anyone can share there Development vs Production
> Application.cfm or .cfc techniques. If you have a sample application.cfm or
> .cfc file to share, then that would be great.
>
> I will give some background as to how I am doing this right now. I usually
> set application variables which of course, have different values in
> development vs production. Best example is pathtoSomething application
> variable's value which would be different in development and production.
>
> Any other advices are also welcome.
>
> Thanks,
>
> Ajas Mohammed.
>
>
>


Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-03 Thread Ajas Mohammed
Thank you everyone. The suggestions  from everyone were very helpful. Using
the suggestions helped me come across these links

http://environmentconfig.riaforge.org/


http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment_Configurations


http://tutorial304.easycfm.com/


http://www.coldfusionjedi.com/index.cfm/2005/9/2/ColdFusion-101-Config-Files-AGoGo-Part-2-XML-Files

Looks
like more people are using or prefer XML. I did see some ppl show hatred
towards XML which is very hard to understand. You would think xml is the
simplest way of storing data or doing things like this. Personally, I would
prefer XML as its easy to work with.

Thanks all,


http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter what, find a way. Because thats what winners do.
You can't improve what you don't measure.
Quality is never an accident; it is always the result of high intention,
sincere effort, intelligent direction and skillful execution; it represents
the wise choice of many alternatives.


On Thu, Oct 29, 2009 at 9:59 AM, Jim Rising  wrote:

> I've been using Coldbox lately and have been making use of the environment
> control interceptors:
>
> http://ortus.svnrepository.com/coldbox/trac.cgi/wiki/cbEnvironmentControl
>
> Previously I had built what essentially amounted to the same idea by
> pulling in environment specific settings via xml onApplicationStart() and
> using a naming convention for the files based on cgi.remote_host and host
> headers setup within apache or IIS. if the browser is looking at
> http://dev.mydomain.com ... app.cfc pulled in '/environments/dev_mydomain_
> com.xml'.
>
> --
> Jim Rising
> Serial Entrepreneur
> Software Engineer
> Web Developer
>
> "Knowledge work requires both autonomy and accountability."
>
>
> On Sat, Oct 24, 2009 at 2:53 PM, Ajas Mohammed  wrote:
>
>> Hi,
>>
>> Just wondering if anyone can share there Development vs Production
>> Application.cfm or .cfc techniques. If you have a sample application.cfm or
>> .cfc file to share, then that would be great.
>>
>> I will give some background as to how I am doing this right now. I usually
>> set application variables which of course, have different values in
>> development vs production. Best example is pathtoSomething application
>> variable's value which would be different in development and production.
>>
>> Any other advices are also welcome.
>>
>> Thanks,
>>
>> Ajas Mohammed.
>>
>>
>>
>
>
>
>


RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread Charlie Arehart
Ajas, you mention some loving/some hating XML files. I didn't see any reply
from you on my note offering yet another alternative (sent 10/24), where I
said simply:

 

"Or one may find it a little easier to use ini files, and CF's functions to
read them (added in CF 6), such as getprofilestring, getprofilesections,
setprofilestring."

 

I'm not knocking any of the solutions you found, nor do I have any hatred
toward XML myself, but I would again argue that for some uses it would
definitely be "easier" than XML. :-) Not as robust or flexible, no. But if
you just want to read in a few strings that would vary in the implementation
of such an ini file would really suit the purpose well. It's just one of the
many easily missed features that CF offers. 

 

Not trying to stop you following the other approaches. Just want to make
sure folks are aware of the alternative. :-)

 

/charlie

 

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed
Sent: Tuesday, November 03, 2009 8:42 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and
other things...

 

Thank you everyone. The suggestions  from everyone were very helpful. Using
the suggestions helped me come across these links

 

http://environmentconfig.riaforge.org/

 

http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment
_Configurations

 

http://tutorial304.easycfm.com/

 

http://www.coldfusionjedi.com/index.cfm/2005/9/2/ColdFusion-101-Config-Files
-AGoGo-Part-2-XML-Files

 

Looks like more people are using or prefer XML. I did see some ppl show
hatred towards XML which is very hard to understand. You would think xml is
the simplest way of storing data or doing things like this. Personally, I
would prefer XML as its easy to work with.

 

Thanks all,






 




-
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-



Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread Ajas Mohammed
Hi Charlie,

I did see your suggestion and I like it as well. Thats why I said thank you
everyone and I didnt pick any single reply/post.

I wasnt aware of using ini file in ColdFusion for config and it was good to
know.

As always, your input was very helpful.

Thanks,

On Wed, Nov 4, 2009 at 11:58 AM, Charlie Arehart wrote:

>  Ajas, you mention some loving/some hating XML files. I didn’t see any
> reply from you on my note offering yet another alternative (sent 10/24),
> where I said simply:
>
>
>
> “Or one may find it a little easier to use ini files, and CF’s functions to
> read them (added in CF 6), such as getprofilestring, getprofilesections,
> setprofilestring.”
>
>
>
> I’m not knocking any of the solutions you found, nor do I have any hatred
> toward XML myself, but I would again argue that for some uses it would
> definitely be “easier” than XML. :-) Not as robust or flexible, no. But if
> you just want to read in a few strings that would vary in the implementation
> of such an ini file would really suit the purpose well. It’s just one of the
> many easily missed features that CF offers.
>
>
>
> Not trying to stop you following the other approaches. Just want to make
> sure folks are aware of the alternative. :-)
>
>
>
> /charlie
>
>
>
> *From:* ad...@acfug.org [mailto:ad...@acfug.org] *On Behalf Of *Ajas
> Mohammed
> *Sent:* Tuesday, November 03, 2009 8:42 PM
> *To:* discussion@acfug.org
> *Subject:* Re: [ACFUG Discuss] Development vs Production Application.cfm
> and other things...
>
>
>
> Thank you everyone. The suggestions  from everyone were very helpful. Using
> the suggestions helped me come across these links
>
>
>
> http://environmentconfig.riaforge.org/
>
>
>
>
> http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment_Configurations
>
>
>
> http://tutorial304.easycfm.com/
>
>
>
>
> http://www.coldfusionjedi.com/index.cfm/2005/9/2/ColdFusion-101-Config-Files-AGoGo-Part-2-XML-Files
>
>
>
> Looks like more people are using or prefer XML. I did see some ppl show
> hatred towards XML which is very hard to understand. You would think xml is
> the simplest way of storing data or doing things like this. Personally, I
> would prefer XML as its easy to work with.
>
>
>
> Thanks all,
>
>
> 
>
>
>
> -
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by FusionLink <http://www.fusionlink.com>
> -
>


RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread Wes Byrd
I use XML (as stated before) but for this single purpose, I agree with Charlie 
that it would be much simpler and just as affective to use the INI file 
functionality built into CF.  You will use half the lines of code to do that vs 
the XML option.

Still, XML is a nice buzz word and if you want to use this as a reason to get 
familiar with reading and parsing XML files, then great!  It is a great 
standard to use for sharing data between systems.  However, again, if the 
purpose is to just read some params in and set application vars, I think the 
ini option Charlie suggested would be best.  I even thought about rewriting my 
system to use the ini rather than the XML.  It would reduce the settings file 
to about 30 lines (60% reduction)  and be MUCH easier to read than my XML.

There is no real answer to which is the "best" option for you.  They are both 
great.



Wes

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Charlie Arehart
Sent: Wednesday, November 04, 2009 10:59 AM
To: discussion@acfug.org
Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and 
other things...

Ajas, you mention some loving/some hating XML files. I didn't see any reply 
from you on my note offering yet another alternative (sent 10/24), where I said 
simply:

"Or one may find it a little easier to use ini files, and CF's functions to 
read them (added in CF 6), such as getprofilestring, getprofilesections, 
setprofilestring."

I'm not knocking any of the solutions you found, nor do I have any hatred 
toward XML myself, but I would again argue that for some uses it would 
definitely be "easier" than XML. :-) Not as robust or flexible, no. But if you 
just want to read in a few strings that would vary in the implementation of 
such an ini file would really suit the purpose well. It's just one of the many 
easily missed features that CF offers.

Not trying to stop you following the other approaches. Just want to make sure 
folks are aware of the alternative. :-)

/charlie

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed
Sent: Tuesday, November 03, 2009 8:42 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and 
other things...

Thank you everyone. The suggestions  from everyone were very helpful. Using the 
suggestions helped me come across these links

http://environmentconfig.riaforge.org/

http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment_Configurations

http://tutorial304.easycfm.com/

http://www.coldfusionjedi.com/index.cfm/2005/9/2/ColdFusion-101-Config-Files-AGoGo-Part-2-XML-Files

Looks like more people are using or prefer XML. I did see some ppl show hatred 
towards XML which is very hard to understand. You would think xml is the 
simplest way of storing data or doing things like this. Personally, I would 
prefer XML as its easy to work with.

Thanks all,




-
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by FusionLink<http://www.fusionlink.com>
-



-

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-




Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread shawn gorrell
Let me throw yet another wrinkle into the discussion. WDDX. There are times 
when I want to have configurations that are represented as complex objects, 
that an INI file cannot do (or at least without pain), and XML parsing is 
horrid at (syntactically). With WDDX I can make a read of the file and a single 
CFWDDX call and I've got native CF datasets to work with like structures, 
arrays and queries, without the pain of XML parsing. I've always thought that 
WDDX is one of the most under-appreciated parts of CF. 





From: Wes Byrd 
To: "discussion@acfug.org" 
Sent: Wed, November 4, 2009 1:17:41 PM
Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and  
other things...

 
I use XML (as stated before) but for this single purpose, I
agree with Charlie that it would be much simpler and just as affective to use
the INI file functionality built into CF.  You will use half the lines of
code to do that vs the XML option.  
 
Still, XML is a nice buzz word and if you want to use this as a
reason to get familiar with reading and parsing XML files, then great!  It
is a great standard to use for sharing data between systems.  However,
again, if the purpose is to just read some params in and set application vars,
I think the ini option Charlie suggested would be best.  I even thought
about rewriting my system to use the ini rather than the XML.  It would
reduce the settings file to about 30 lines (60% reduction)  and be MUCH
easier to read than my XML.
 
There is no real answer to which is the "best" option
for you.  They are both great.
 

 
Wes
 
From:ad...@acfug.org
[mailto:ad...@acfug.org] On Behalf Of Charlie Arehart
Sent: Wednesday, November 04, 2009 10:59 AM
To: discussion@acfug.org
Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm
and other things...
 
Ajas, you mention some loving/some hating XML files. I
didn’t see any reply from you on my note offering yet another alternative
(sent 10/24), where I said simply:
 
“Or one may find it a little easier to use ini files, and
CF’s functions to read them (added in CF 6), such as getprofilestring,
getprofilesections, setprofilestring.”
 
I’m not knocking any of the solutions you found, nor do I
have any hatred toward XML myself, but I would again argue that for some uses
it would definitely be “easier” than XML. :-) Not as robust or
flexible, no. But if you just want to read in a few strings that would vary in
the implementation of such an ini file would really suit the purpose well.
It’s just one of the many easily missed features that CF offers. 
 
Not trying to stop you following the other approaches. Just want
to make sure folks are aware of the alternative. :-)
 
/charlie
 
From:ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed
Sent: Tuesday, November 03, 2009 8:42 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm
and other things...
 
Thank you everyone. The suggestions  from everyone were
very helpful. Using the suggestions helped me come across these links
 
http://environmentconfig.riaforge.org/
 
http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment_Configurations
 
http://tutorial304.easycfm.com/
 
http://www.coldfusionjedi.com/index.cfm/2005/9/2/ColdFusion-101-Config-Files-AGoGo-Part-2-XML-Files
 
Looks like more people are using or prefer XML. I did see
some ppl show hatred towards XML which is very hard to understand. You would
think xml is the simplest way of storing data or doing things like this.
Personally, I would prefer XML as its easy to work with.
 
Thanks all,


 

- 
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform 

For more info, see http://www.acfug.org/mailinglists 
Archive @ http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by FusionLink 
- 
- 
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform 

For more info, see http://www.acfug.org/mailinglists 
Archive @ http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by FusionLink 
-


-

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-




RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread Charlie Arehart
Good point. I did say I realized that ini files weren’t as “robust or 
flexible”. :-) But WDDX files are definitely a step above that before making up 
one’s own XML. They all have their place, so good to be reminded every once in 
a while. 

 

And thanks for the concurrence on INI files, Wes. :-)

 

/charlie

 

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of shawn gorrell
Sent: Wednesday, November 04, 2009 1:29 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and 
other things...

 

Let me throw yet another wrinkle into the discussion. WDDX. There are times 
when I want to have configurations that are represented as complex objects, 
that an INI file cannot do (or at least without pain), and XML parsing is 
horrid at (syntactically). With WDDX I can make a read of the file and a single 
CFWDDX call and I've got native CF datasets to work with like structures, 
arrays and queries, without the pain of XML parsing. I've always thought that 
WDDX is one of the most under-appreciated parts of CF. 




-

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-




Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread shawn gorrell
I've actually got an initialization customtag that does xml or wddx if anyone 
is interested. 





From: Charlie Arehart 
To: discussion@acfug.org
Sent: Wed, November 4, 2009 5:18:46 PM
Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and  
other things...

 
Good point. I did say I realized that ini files weren’t as “robust
or flexible”. :-) But WDDX files are definitely a step above that before making
up one’s own XML. They all have their place, so good to be reminded every once
in a while. 
 
And thanks for the concurrence on INI files, Wes. :-)
 
/charlie
 
From:ad...@acfug.org
[mailto:ad...@acfug.org] On Behalf Of shawn gorrell
Sent: Wednesday, November 04, 2009 1:29 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm
and other things...
 
Let
me throw yet another wrinkle into the discussion. WDDX. There are times when I
want to have configurations that are represented as complex objects, that an
INI file cannot do (or at least without pain), and XML parsing is horrid at
(syntactically). With WDDX I can make a read of the file and a single CFWDDX
call and I've got native CF datasets to work with like structures, arrays and
queries, without the pain of XML parsing. I've always thought that WDDX is one
of the most under-appreciated parts of CF. 
- 
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform 

For more info, see http://www.acfug.org/mailinglists 
Archive @ http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by FusionLink 
-


-

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-




Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-11-04 Thread Ajas Mohammed
Hi,

Please send it my way. Much appreciated. :-)

On Wed, Nov 4, 2009 at 5:22 PM, shawn gorrell  wrote:

> I've actually got an initialization customtag that does xml or wddx if
> anyone is interested.
>
> --
> *From:* Charlie Arehart 
> *To:* discussion@acfug.org
> *Sent:* Wed, November 4, 2009 5:18:46 PM
> *Subject:* RE: [ACFUG Discuss] Development vs Production Application.cfm
> and other things...
>
>  Good point. I did say I realized that ini files weren’t as “robust or
> flexible”. :-) But WDDX files are definitely a step above that before making
> up one’s own XML. They all have their place, so good to be reminded every
> once in a while.
>
>
>
> And thanks for the concurrence on INI files, Wes. :-)
>
>
>
> /charlie
>
>
>
> *From:* ad...@acfug.org [mailto:ad...@acfug.org] *On Behalf Of *shawn
> gorrell
> *Sent:* Wednesday, November 04, 2009 1:29 PM
> *To:* discussion@acfug.org
> *Subject:* Re: [ACFUG Discuss] Development vs Production Application.cfm
> and other things...
>
>
>
> Let me throw yet another wrinkle into the discussion. WDDX. There are times
> when I want to have configurations that are represented as complex objects,
> that an INI file cannot do (or at least without pain), and XML parsing is
> horrid at (syntactically). With WDDX I can make a read of the file and a
> single CFWDDX call and I've got native CF datasets to work with like
> structures, arrays and queries, without the pain of XML parsing. I've always
> thought that WDDX is one of the most under-appreciated parts of CF.
>
> -
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by FusionLink <http://www.fusionlink.com>
> -
>
> -
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by FusionLink <http://www.fusionlink.com>
> -
>


re[2]: [ACFUG Discuss] Development vs Production Application.cfm and other things...

2009-10-28 Thread Mischa Uppelschoten



FWIW, I am creating application objects
 in application.cfc
 
application.Order = createobject("Component",
 #application.ComponentsLocation# & "Order");
 
this way CF doesn't have to create and
 destroy these static objects all the time.
 For development this doesn't work so well
 because you'd have to reload your application
 vars every time you change one of these static
 cfc's. To help with that, I have defined
 an OnRequestStart function that does this.
 There is of course a performance penalty,
 but for dev that doesn't matter:
 
 
 
 
HTH
/m
 
: I like to keep the application.cfc
 the same and use an XML file to store the:
  application variables and their values
 that differ on each machine.  So, in:
  the application.cfc on application
 start, you can execute a component that:
  can parsethe XML and set application
 scope vars accordingly. :   :
 Wes :   :  : From:
 ad...@acfug.org
 [mailto:ad...@acfug.org]
 On Behalf Of Ajas Mohammed:  Sent:
 Saturday, October 24, 2009 3:53 PM:  To:
 discussion@acfug.org:
  Subject: [ACFUG Discuss] Development
 vs Production Application.cfm and other:
  things... :   : Hi,
 :  :   :  :
 Just wondering if anyone can share there
 Development vs Production:  Application.cfm
 or .cfc techniques. If you have a sample
 application.cfm or:  .cfc file to
 share, then that would be great.   :
  :   :  :
 I will give some background as to how I am
 doing this right now. I usually set:
  application variables which of course,
 have different values in:
  development vs production. Best example
 is pathtoSomething application:  variable's
 value which would be different in development
 and production. :  :   :
  : Any other advices are also welcome.
 :  :   :  :
 Thanks, :  :   :
  : Ajas Mohammed. :  :
   :  Mischa
 UppelschotenVP of TechnologyThe Banker's
 Exchange, LLC.4200 Highlands Parkway
 SESuite ASmyrna, GA 30082-5198Phone:(404)
 605-0100 ext. 10Fax:(404)
 355-7930Web:www.BankersX.comFollow
 this link for Instant Web Chat:http://www.bankersx.com/Contact/chat.cfm?Queue=MUPPELSCHOTEN

--- Original
 Message ---
  
From: Wes Byrd 
To: "discussion@acfug.org"
 
Date: Sat, 24 Oct 2009 17:02:46
 -0500
Subject: RE: [ACFUG Discuss]
 Development vs Production Application.cfm
 and other things...
  

I like to keep the application.cfc
 the same and use an XML file to store the
 application variables and their values that
 differ on each machine.  So, in the
 application.cfc on application start, you
 can execute a component that can parse the
 XML and set application scope vars accordingly.
 
Wes
 

From:
 ad...@acfug.org [mailto:ad...@acfug.org]
 On Behalf Of Ajas MohammedSent:
 Saturday, October 24, 2009 3:53 PMTo:
 discussion@acfug.orgSubject: [ACFUG
 Discuss] Development vs Production Application.cfm
 and other things...
 
Hi,

 

Just wondering if anyone
 can share there Development vs Production
 Application.cfm or .cfc techniques. If you
 have a sample application.cfm or .cfc file
 to share, then that would be great. 
 

 

I will give some background
 as to how I am doing this right now. I usually
 set application variables which of course,
 have different values     in development
 vs production. Best example is pathtoSomething
 application variable's value which would
 be different in development and production.

 

Any other advices are
 also welcome.

 

Thanks,

 

Ajas Mohammed.

 

 -
 To unsubscribe from this list, manage
 your profile @ http://www.acfug.org?fa=login.edituserform
 For more info, see http://www.acfug.org/mailinglists
 Archive @ http://www.mail-archive.com/discussion%40acfug.org/
 List hosted by FusionLink -



-
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-