I wonder which way is the best and faster:
1. Create one component to execute any sql command and reuse it for entire 
system.
2. Create each component for each task - like component to load country 
name, another component to load something else.

Please advice,

Hi:
     I don´t know if the link below it will be usefull for you but it got some
good tips for developing in ASP.
     One more thing, if the componente that you will need to use is an ADO
object, it keeps an internal pool,
where he manages the connections (and other things?).

Marcelo

http://search.microsoft.com/gomsuri.asp?n=1&c=rp_Results&siteid=us&target=http://msdn.microsoft.com/library/en-us/dnasp/
html/asptips.asp







not24@h... on 19/02/2003 16:10:22

Please respond to "ASP components" <asp_components@p...>

To:   "ASP components" <asp_components@p...>
cc:    (bcc: Marcelo Adrián Zanolin/Red Link S.A.)

Subject:  [asp_components] What's best of using components in ASP?




I wonder which way is the best and faster:
1. Create one component to execute any sql command and reuse it for entire
system.
2. Create each component for each task - like component to load country
name, another component to load something else.

Please advice,

zanolin_marcelo@r...
To unsubscribe send a blank email to %%email.unsub%%

As long as it doesn't get silly in size, I'd use just the one component
for everything.  Not only will it be easier to manage, but IIS keeps
DLLs loaded in memory even when you have finished with them (try
replacing a DLL that IIS has used) so the next time you come to use it
it loads faster.  If everything is in one DLL then once you have used it
once, subsequent uses should be faster.

-----Original Message-----
From: Marcelo Adri=E1n Zanolin [mailto:zanolin_marcelo@r...]
Sent: 19 February 2003 7:06
To: ASP components
Subject: [asp_components] Re: What's best of using components in ASP?





Hi:
     I don=B4t know if the link below it will be usefull for you but it
got some good tips for developing in ASP.
     One more thing, if the componente that you will need to use is an
ADO object, it keeps an internal pool, where he manages the connections
(and other things?).

Marcelo

http://search.microsoft.com/gomsuri.asp?n=3D1&c=3Drp_Results&siteid=3Dus&
targe
t=3Dhttp://msdn.microsoft.com/library/en-us/dnasp/html/asptips.asp







not24@h... on 19/02/2003 16:10:22

Please respond to "ASP components" <asp_components@p...>

To:   "ASP components" <asp_components@p...>
cc:    (bcc: Marcelo Adri=E1n Zanolin/Red Link S.A.)

Subject:  [asp_components] What's best of using components in ASP?




I wonder which way is the best and faster:
1. Create one component to execute any sql command and reuse it for
entire system. 2. Create each component for each task - like component
to load country name, another component to load something else.

Please advice,

zanolin_marcelo@r... 
%%email.unsub%%

---
Change your mail options at http://p2p.wrox.com/manager.asp or to
unsubscribe send a blank email to 







adrian.forbes@n... 
%%email.unsub%%