OK I get it .. but not really. I was thrown off by your showing of the XML handling in a regular ASP page.

I have no idea how you would do that. I wonder what is the advantage of using something like foxISAPI. Why are you using it? (just curious))

>>>>Yeah I saw that, but I think I remember another thread where you more or less asked the same question. I may be wrong, it could've been somebody else.
>>>
>>>One question I am planning on asking is how a VFP MTDLL ISAPI (foxISAP) server can send an XML string to a browser client. Not ready to ask it yet - but pretty soon!
>>
>>Are you joking with me or at me? *g*
>
>I really don't know - the server to client tranasaction seems obvious: all it needs is a URL with an XML. It could be stashed upon receipt in a DIV or some "inner text" apparatus (the GUI is HTML/JS).
>
>But sending it to the foxISAPI, or Client to server tansaction. My only experience sending stuff to foxISAPI is a javascript URL with standard parameter structure. But how to send an XML to a foxISAPI server that does not have a "request" apparatus, like ASP, to receive an XML structure. The client html (ecma) script can create an XMLHTTP, but how to pass it to a VFP isapi server outside the "usual" URL method:

>*This is what a foxISAPI server "deposit" looks like:
>cURL="http://www.BigCityDNS.com/scripts/foxISAPI.dll/myVFPServer.Application.SetChoice?";
>    +"accountid="+theAccountID+"&userid="+theUserID+"&cpwd="+thePwd;
>    +"&activityid="+theActivityID;
>
>* Heres what the method looks like in the VFP isapiCOM
>PROCEDURE SetChoice
>LPARAMETERS lcFormsVars,lcIniFile,lnReleaseFlag
>LOCAL lcOutput
>SET PATH TO (this.cScriptsPath)
>SYS(2336,1)
>WITH this
>SetActivityPage(lcFormsVars,.cAccountUrlPath,.cDataPath+[accountinfo],;
>.cDataPath+[COM_login],.cDataPath+[iteminfo],.cDataPath+[userinfo])
>
>lcOutput=GetContentPage(lcFormsVars,.cAccountUrlPath,.cDataPath+[accountinfo],;
>         .cDataPath+[COM_login],.cDataPath+[iteminfo],.cDataPath+[userinfo])
>ENDWITH
>SYS(2336,2)
>RETURN lcOutput
>ENDPROC &&SetActivity

>There is the risk that in some cases, the xml may require more capacity than allowed by URL or lcFormsVars. If you could share something I could look at to help me understand how a VFP isapiCOM could receive an XML, I would be more than greatful - I'll double the delivery of Rubin's dirty deeds! This project does not allow for ASP or JSP - everything is JS and VFP ISAPI COM. MS DOM and MS HTTP can be instanciated at both client and server. Any ideas?