.NET components for performance or convenience?

> Up till now we've been calling compenents from ASP for
> mostly performance reasons. Now that aspx pages are
> compiled does that negate the performance issue? We'll
> still use components because we like the separation of
> logic from interface, but will there also be some kind of
> performance advantage?

From what I've read, ASP+ pages are compiled the first time they are
requested through IIS. In addition to compilation, you can implicitly
declare the page (or parts of) to be cached in memory. An article posted
on MSDN today
(http://msdn.microsoft.com/msdnmag/issues/0900/ASPPlus/ASPPlus.asp)
describes 3 types of caching that are available in the ASP+ environment.

You raise a very interesting question about performance. Personally, I
would like to know if unsafe components run in the managed runtime
environment of ASP+. If that's the case, then I can't see a big-time
performance benefit. If (however) you can somehow implicitly declare a
component to run in an unmanaged state ( la the "unsafe" keyword in
C#), then I would hazard to guess that you'd see significant performance
boosts over components running in a managed environment (CLR).

The biggest benefit I see about ASP+ are the web controls, IMHO. The ASP
namespace provides 5 types:

* 1:1 HTML equivalents
* list controls
* rich controls
* validation controls
* mobile controls

The last 2 are the really cool ones, me thinks. ;-) I haven't seen any
documentation on mobile controls on MSDN as of yet. Any one know where I
can find examples?

John

Plus there's the scalability of COM+ (ie, easy to load balance and add
multiple machines to spread out the processing). Does anyone know if ASP+
gives anything new in terms of scalability?

Greg

"PBSOFT" <Felkins@pbsoft.net> wrote in message
news:3992b81b@news.dev-archive.com...
>
> You may still decide that components are a good thing , IMHO - they are --
> components can take advantage of com+ and mts specific features as object
> pooling and connection pooling -- not real sure if you can do this on a
asp
> page -- and if you could, to what good it would do -- and using components
> does force a certain amount of reusable code -- so they are a very good
thing
>
> "John Bristowe" <john.bristowe@cf.com.au> wrote:
> >> Up till now we've been calling compenents from ASP for
> >> mostly performance reasons. Now that aspx pages are
> >> compiled does that negate the performance issue? We'll
> >> still use components because we like the separation of
> >> logic from interface, but will there also be some kind of
> >> performance advantage?
> >
> >From what I've read, ASP+ pages are compiled the first time they are
> >requested through IIS. In addition to compilation, you can implicitly
> >declare the page (or parts of) to be cached in memory. An article posted
> >on MSDN today
> >(http://msdn.microsoft.com/msdnmag/issues/0900/ASPPlus/ASPPlus.asp)
> >describes 3 types of caching that are available in the ASP+ environment.
> >
> >You raise a very interesting question about performance. Personally, I
> >would like to know if unsafe components run in the managed runtime
> >environment of ASP+. If that's the case, then I can't see a big-time
> >performance benefit. If (however) you can somehow implicitly declare a
> >component to run in an unmanaged state ( la the "unsafe" keyword in
> >C#), then I would hazard to guess that you'd see significant performance
> >boosts over components running in a managed environment (CLR).
> >
> >The biggest benefit I see about ASP+ are the web controls, IMHO. The ASP
> >namespace provides 5 types:
> >
> >* 1:1 HTML equivalents
> >* list controls
> >* rich controls
> >* validation controls
> >* mobile controls
> >
> >The last 2 are the really cool ones, me thinks. ;-) I haven't seen any
> >documentation on mobile controls on MSDN as of yet. Any one know where I
> >can find examples?
> >
> >John
> >
> >
>

"PBSOFT" <Felkins@pbsoft.net> wrote in message
news:3992b81b@news.dev-archive.com...
>
> You may still decide that components are a good thing , IMHO - they are --
> components can take advantage of com+ and mts specific features as object
> pooling and connection pooling -- not real sure if you can do this on a
asp
> page

All can be done from an ASP+ page I believe. Connection pooling happens at
the OLEDB layer in any case. Object Pooling happens behind the activation
so ASP+ pages just rely on the facilities. Neither of these are specific to
components.