VB COM, Pass ASP Intrinsics to Com component by ref?

Pass ASP Intrinsics to Com component by ref?

Author	Message
msnews.microsoft.co #1 / 3	Pass ASP Intrinsics to Com component by ref? Hello, A friend has run across an application that passes the four big ASP intrinsic objects (request,response,session,application) to a VB com component, e.g. He's looking for some advice from me. Here is an example call from ASP to an example component. dim myObj set myObj=Server.CreateObject("Mylib.MyObj") Response.write myObj.DoWork(Request,Application, Response, Server) The only (modern) way I've ever done or seen this done is through the ObjectContext to get references to the objects, which requests referencing the MTS/COM+ typelib and being a configured component. That is, not passing the intrinsics as parameters. Now, this app does run totally in process (runs in IIS process space, component is not in mts, it is just an ActiveX DLL.) So, it isn't doing cross process calls, at least, not obviously so. Nonetheless, this approach makes me very anxious for a reasons I can't put my finger on. Am I being paranoid about this, or is there really some reason why this is bad? Obviously, it would be very bad if these components were ever being run in MTS... Thanks for any thoughts, Brian
Mon, 15 Sep 2003 22:59:06 GMT

Adrian Forbe #2 / 3	Pass ASP Intrinsics to Com component by ref? Microsoft recommends you use the ObjectContext way of getting the intrinsic objects. AFAIK it has never recommended you pass the objects as parameters, before you could use ObjectContext you were supposed to use OnStartPage. If you search MS's site they may explain why you should use the ObjectContext method. Quote: > Hello, > A friend has run across an application that passes the four big ASP > intrinsic objects (request,response,session,application) to a VB com > component, e.g. He's looking for some advice from me. > Here is an example call from ASP to an example component. > dim myObj > set myObj=Server.CreateObject("Mylib.MyObj") > Response.write myObj.DoWork(Request,Application, Response, Server) > The only (modern) way I've ever done or seen this done is through the > ObjectContext to get references to the objects, which requests referencing > the MTS/COM+ typelib and being a configured component. That is, not passing > the intrinsics as parameters. > Now, this app does run totally in process (runs in IIS process space, > component is not in mts, it is just an ActiveX DLL.) So, it isn't doing > cross process calls, at least, not obviously so. > Nonetheless, this approach makes me very anxious for a reasons I can't put > my finger on. Am I being paranoid about this, or is there really some reason > why this is bad? Obviously, it would be very bad if these components were > ever being run in MTS... > Thanks for any thoughts, > Brian
Mon, 15 Sep 2003 23:29:12 GMT

msnews.microsoft.co #3 / 3	Pass ASP Intrinsics to Com component by ref? Thanks, this is what my research discovered: 1. Prior to ObjectContext you use OnStartPage 2. Now all samples and advice indicates ObjectContext searching Google, MSDN, usenet, everybody says use ObjectContext...but no one says "DON'T pass this way even if you are inprocess..." Still... Quote: > Microsoft recommends you use the ObjectContext way of getting the intrinsic > objects. AFAIK it has never recommended you pass the objects as parameters, > before you could use ObjectContext you were supposed to use OnStartPage. If > you search MS's site they may explain why you should use the ObjectContext > method. > > Hello, > > A friend has run across an application that passes the four big ASP > > intrinsic objects (request,response,session,application) to a VB com > > component, e.g. He's looking for some advice from me. > > Here is an example call from ASP to an example component. > > dim myObj > > set myObj=Server.CreateObject("Mylib.MyObj") > > Response.write myObj.DoWork(Request,Application, Response, Server) > > The only (modern) way I've ever done or seen this done is through the > > ObjectContext to get references to the objects, which requests referencing > > the MTS/COM+ typelib and being a configured component. That is, not > passing > > the intrinsics as parameters. > > Now, this app does run totally in process (runs in IIS process space, > > component is not in mts, it is just an ActiveX DLL.) So, it isn't doing > > cross process calls, at least, not obviously so. > > Nonetheless, this approach makes me very anxious for a reasons I can't put > > my finger on. Am I being paranoid about this, or is there really some > reason > > why this is bad? Obviously, it would be very bad if these components were > > ever being run in MTS... > > Thanks for any thoughts, > > Brian
Tue, 16 Sep 2003 01:47:20 GMT

Page 1 of 1

[ 3 post ]