First two replies were screwed up, apoligies....


Rick, I was doing some more digging here on the UT and found a message from a guy who was/is thinking the same as me. What I would like to do is use ASP/VBScript for all page display (and sessions/cookies), but no data manipulation or business rules. Going through your FoxISAPI document and your book, it looks like I have to use my VFP .EXEs to pass HTTP-encoded HTML thru FoxISAPI to the browser, which isn't exactly what I am looking for; what I am looking for is a way to pass unformatted arrays of info to ASP pages and let the page formatting, etc occur there. I am in a heavy VBScripter environment now and have about 0% control over the presentation tier of the web applications made here.

An abstract of my thinking is like this:

 %%aspcodeblock%%
    1  Dimension arData
    2  oThing = Server.CreateObject(foxisapisomething)
    3  oThing.foxisapi.method.call.to.vfpexe
    4  (capture the return info into the arData array)
    5  (parse the array based on what's in it)
    6  response.write the array into an HTML table
  %%aspcodeblock

Having the things setup in this method allows me to control lines 1-5 but lets the VBScripters (web designers) influence lines 5-6.
Message #318417 is below for reference.
Please help, thanks!




>Thanks for the info!
>
>Now, on to something else FoxISAPI related....
>
>I don't want to use FoxISAPI to return an entire http-wrapped, html-ized string. I want it to just return an array of strings to my ASP page, which I will then format, etc as I need to.

I'm not sure what you're saying. If you need to call a VFP component just call it directly from the ASP page. If you need a distributed application return the data as you need from the other Web server...




Message #318417
From 2000/01/14 7:03:37 pm Mark Frank #001422

>Robert, I think that Mark was asking how to take advantage of FoxISAPI's pool manager from ASP. Instanciating an object directly from the page won't help here. Mark- if you are still in the beginning phases of this project, I highly recommend having a look at Web Connection. Rick has built his own pool managaer that is more efficient than both MTS and FoxISAPI.

Erik is right on. Here's the quandry I'm in. I know Rick has a pool manager but my understanding is that he also his own session management and session-level variable management that is independent of ASP and ASP's session objects. What I want is to leverage the pool manager (probably solely) to take advantage of the VFP engine and related data-centric business logic that would be embedded in my out-of-process server(s). But I would like to use ASP/Web classes to coordinate the session management. I want to be able to pass the Session, Request, and Response objects from ASP to the methods in my out-of-process server(s) which will be sitting there, already instantiated, with databases open and ready to fly. Or stated a bit differently, I want the same functionality that one can derive from an in-process VFP MT DLL that is easily joined with an ASP/WebClass app... but as an alternative, I want this functionality in conjunction with using pooled, out-of-process servers rather than repeatedly re-instantiating objects within MT DLL in-process servers. Rick has proven (to me, anyway) that this technique provides more bang for the buck.