The HTTP interface, where you receive a request and are writing to %print_fn with the html (or xml or json or whatever) that you want to return... does it have to be Apache?  In the documentation there's clearly scripting info in a .cgi file to say start PxPlus and runs *plus/apache/pxp_cgi.  Is there anything in there that requires Apache rather than a different web server?  For example, could I have an equivalent script in IIS that runs PxPlus *plus/apache/pxp_cgi and it will forward the web request and return the response to IIS?

I'm trying to integrate my iNomads application with a third party API.  Using the *browser object, I get an iframe that navigates to the other website where the user can enter data and we get an Ajax response.  I'm able to parse this response and put the data I need into multi-lines on the iNomads page.  What I haven't been able to figure out though is how to post that data back to PxPlus process to use.  If I click into the field and press enter the on it looks like the data for that field gets pushed and the onchange logic fires off.  Is there a way (presumably in javascript) to simulate this or otherwise push the data?

I'm getting mixed results trying to navigate to sites with a reCAPTCHA using *browser.  I think it might be version based.  I have a client running v14 and the reCAPTCHA won't load but in my office on v16 it does.  Captchas have been around for ages so I'm a little surprised that an older version of *browser wouldn't be able to handle it.  Are you aware of anything that may have changed between versions that would allow reCAPTCHA to start working?  Is there a minimum version for this or a setting to turn on so the old version will display properly?
Thanks,

We have code writing to a database using the [odb] tag.  It works well generally, however at one client, they are using a MySQL server.  MySQL needs backslashes to be escaped (especially at the end of a field where it would end up escaping the quote delimiters).  If using the [odb] tag, a backslash in data is not getting escaped.  Would using the [mysql] tag instead resolve this?  Is there an option or setting that would let us use the [odb] tag still but correctly escape the backslashes?

At one of our clients, we're trying to communicate with a device via TCP but the connection isn't great.  We're having difficulty telling if the device is still working on the command and hasn't replied yet or if the connection has dropped.  The basic code looks like:

write record(tcp_chan)"command goes here"
while 1
read record(tcp_chan,tim=5)resp_segment$
let response$+=resp_segment$
if pos(end_of_message$=response$) then goto *break
wend

If the connection has dropped we want to know as soon as possible and then we can try re-opening the channel, request the last command, prompt the user to reset the device etc.  Without a tim= branch we can sit there way too long.  However the device may legitimately take a long time to process the command, especially if human interaction is involved it could take well over a minute.

Is there a way to determine if the connection has dropped or if the device is just taking a long time to process?

DUMP GOTO looks like it would be really useful for debugging... but the results I'm getting are basically pages and pages of *winproc... is there another parameter that says don't track jump history in system programs?

Mainly looking for best practices when using the %inomads'upload_file() method.  We want to limit file type and file size on an upload.  We'd also want to scan the file for viruses.  I don't see anything in the inomads documentation that does any of this.  Is there a way to limit file type/size.  Can iNomads integrate with a virus scanner?