hi
how much overhead
or performance i lose
with the next configuration ? :

1- IIS starts the USER_X.asp page
[ with exec permissions for IUSR ]
2- USER_X.asp creates an out-of-proc object called PROXY_X
[ PROXY_X runs under a PROFILE_X account ]
[ IWAM has exec permissons for PROXY_X ]
3- USER_X.asp invoke "sp_userx_..." stored procedures thru PROXY_X
[ PROXY_X has exec permissions for "sp_userx_..." ]
4- and the same again for every user type x, y, z

it has not the big scalability
but its enough in my case

this is intended for security reasons
i neer to know your opinions about
this configuration please

thanks

Impersonating and running through a proxy and out of proc, may slow down by
3 times.
to know exact numbers, just run WAST (free download) from
http://downloads.microsoft.com
[color=blue]
> it has not the big scalability
> but its enough in my case[/color]
So, why worry?

--
compatible web farm Session replacement for Asp and Asp.Net
http://www.nieropwebconsult.nl/asp_session_manager.htm

"Hernán Castelo" <hcastelo@cedi.frba.utn.edu.ar> wrote in message
news:uAnGEfYTEHA.1768@TK2MSFTNGP10.phx.gbl...[color=blue]
> hi
> how much overhead
> or performance i lose
> with the next configuration ? :
>
> 1- IIS starts the USER_X.asp page
> [ with exec permissions for IUSR ]
> 2- USER_X.asp creates an out-of-proc object called PROXY_X
> [ PROXY_X runs under a PROFILE_X account ]
> [ IWAM has exec permissons for PROXY_X ]
> 3- USER_X.asp invoke "sp_userx_..." stored procedures thru PROXY_X
> [ PROXY_X has exec permissions for "sp_userx_..." ]
> 4- and the same again for every user type x, y, z
>
> it has not the big scalability
> but its enough in my case
>
> this is intended for security reasons
> i neer to know your opinions about
> this configuration please
>
> thanks
>
>[/color]