By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,262 Members | 1,128 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,262 IT Pros & Developers. It's quick & easy.

How to Load Website Properties and Store Them All at Once?

P: n/a
I have some properties data to be loaded for the site use, such as:
website url, admin email, mailing component to use, etc. for my ASP
website. They will be stored in a database, or I also consider XML and/
or .inc text file.
What is the best practice to load them once when user starts website
browsing and keep them until user leaves the site?
I considered Global.asa, but I know there must be one per application.
I may have 2 same applications or more under different directories
thus more than 1 asa will be used.
Should I use "session" or "application" objects and how to use them
for my case?
Should I consider XML or text file instead of database? How faster are
they if I consider under 10 properties to store?
Thanks for any advice.
Jul 21 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a

"vunet" <vu******@gmail.comwrote in message
news:5c**********************************@f36g2000 hsa.googlegroups.com...
I have some properties data to be loaded for the site use, such as:
website url, admin email, mailing component to use, etc. for my ASP
website. They will be stored in a database, or I also consider XML and/
or .inc text file.
What is the best practice to load them once when user starts website
browsing and keep them until user leaves the site?
I considered Global.asa, but I know there must be one per application.
I may have 2 same applications or more under different directories
thus more than 1 asa will be used.
Should I use "session" or "application" objects and how to use them
for my case?
Should I consider XML or text file instead of database? How faster are
they if I consider under 10 properties to store?
If you have multiple applications that wish to share settings then its best
to store them in a DB.

Load them into the application object on application start using the
Global.asa.

--
Anthony Jones - MVP ASP/ASP.NET
Jul 22 '08 #2

P: n/a
On Jul 22, 8:03*am, "Anthony Jones" <A...@yadayadayada.comwrote:
"vunet" <vunet...@gmail.comwrote in message

news:5c**********************************@f36g2000 hsa.googlegroups.com...
I have some properties data to be loaded for the site use, such as:
website url, admin email, mailing component to use, etc. for my ASP
website. They will be stored in a database, or I also consider XML and/
or .inc text file.
What is the best practice to load them once when user starts website
browsing and keep them until user leaves the site?
I considered Global.asa, but I know there must be one per application.
I may have 2 same applications or more under different directories
thus more than 1 asa will be used.
Should I use "session" or "application" objects and how to use them
for my case?
Should I consider XML or text file instead of database? How faster are
they if I consider under 10 properties to store?

If you have multiple applications that wish to share settings then its best
to store them in a DB.

Load them into the application object on application start using the
Global.asa.

--
Anthony Jones - MVP ASP/ASP.NET
If I use my app on a few other servers, then is it true I cannot use
Global.asa without its modification? In other words, can I pack my app
with Global.asa and distribute to whatever I want? I thought I cannot.
Thanks.
Jul 22 '08 #3

P: n/a
vunet wrote:
On Jul 22, 8:03 am, "Anthony Jones" <A...@yadayadayada.comwrote:
>"vunet" <vunet...@gmail.comwrote in message

news:5c**********************************@f36g2000 hsa.googlegroups.com...
>>
>>I have some properties data to be loaded for the site use, such as:
website url, admin email, mailing component to use, etc. for my ASP
website. They will be stored in a database, or I also consider XML
and/ or .inc text file.
What is the best practice to load them once when user starts website
browsing and keep them until user leaves the site?
I considered Global.asa, but I know there must be one per
application. I may have 2 same applications or more under different
directories thus more than 1 asa will be used.
Should I use "session" or "application" objects and how to use them
for my case?
Should I consider XML or text file instead of database? How faster
are they if I consider under 10 properties to store?

If you have multiple applications that wish to share settings then
its best to store them in a DB.

Load them into the application object on application start using the
Global.asa.

--
Anthony Jones - MVP ASP/ASP.NET

If I use my app on a few other servers, then is it true I cannot use
Global.asa without its modification? In other words, can I pack my app
with Global.asa and distribute to whatever I want? I thought I cannot.
I do it all the time. What gave you the idea that you couldn't?
You cannot access another application's global.asa, but you can
certainly copy the file into another application ...

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Jul 22 '08 #4

P: n/a
On Jul 22, 10:23*am, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
vunet wrote:
On Jul 22, 8:03 am, "Anthony Jones" <A...@yadayadayada.comwrote:
"vunet" <vunet...@gmail.comwrote in message

news:5c**********************************@f36g2000 hsa.googlegroups.com...


>I have some properties data to be loaded for the site use, such as:
website url, admin email, mailing component to use, etc. for my ASP
website. They will be stored in a database, or I also consider XML
and/ or .inc text file.
What is the best practice to load them once when user starts website
browsing and keep them until user leaves the site?
I considered Global.asa, but I know there must be one per
application. I may have 2 same applications or more under different
directories thus more than 1 asa will be used.
Should I use "session" or "application" objects and how to use them
for my case?
Should I consider XML or text file instead of database? How faster
are they if I consider under 10 properties to store?
If you have multiple applications that wish to share settings then
its best to store them in a DB.
Load them into the application object on application start using the
Global.asa.
--
Anthony Jones - MVP ASP/ASP.NET
If I use my app on a few other servers, then is it true I cannot use
Global.asa without its modification? In other words, can I pack my app
with Global.asa and distribute to whatever I want? I thought I cannot.

I do it all the time. What gave you the idea that you couldn't?
You cannot access another application's global.asa, but you can
certainly copy the file into another application ...

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
So if I understand this should be possible:

my web site is under folder "mysite" and it contains Global.asa as in
"mysite/Global.asa". I make 2 copies of my site like this:

root/website1/mysite/
and
root/website2/mysite/

where Global.asa will be under each mysite folder. Is this a correct
idea? Please confirm. But then how does the server know where to find
Global.asa? Especially if I have no access to web server admin rights?
Thanks
Jul 22 '08 #5

P: n/a
vunet wrote:
On Jul 22, 10:23 am, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
>vunet wrote:
>>On Jul 22, 8:03 am, "Anthony Jones" <A...@yadayadayada.comwrote:
"vunet" <vunet...@gmail.comwrote in message

news:5c**********************************@f36g2000 hsa.googlegroups.com...
>>

>>If I use my app on a few other servers, then is it true I cannot use
Global.asa without its modification? In other words, can I pack my
app with Global.asa and distribute to whatever I want? I thought I
cannot.

I do it all the time. What gave you the idea that you couldn't?
You cannot access another application's global.asa, but you can
certainly copy the file into another application ...
So if I understand this should be possible:

my web site is under folder "mysite" and it contains Global.asa as in
"mysite/Global.asa". I make 2 copies of my site like this:

root/website1/mysite/
and
root/website2/mysite/

where Global.asa will be under each mysite folder. Is this a correct
idea? Please confirm. But then how does the server know where to find
Global.asa? Especially if I have no access to web server admin rights?
Thanks
Sure, why not? As long as each one is defined as an application using
IIS Manager, there is not issue here.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Jul 22 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.