@Darren L <..>
Oliver - easily said, & it's been suggested that "handlespecialurl" be used in the web app to receive the data... but... I'm not sure how this works when there could be 10's if not hundreds of clients sending data (~100 bytes) to web app at same time. How will handlespecialurl cope this this amount of data?
Because this is an application-level URL, the event is handled without a session context. Unhandled exceptions will be handled by WebApplication.UnhandledException. If you return False from WebApplication.UnhandledException this event will output Internal Server Error html. This will not cause your app to terminate.
Calls to this event are threaded so that simultaneous calls from clients can be handled properly.
In CGI mode, the headers sent with the WebRequest object have the same limitations as they do in WebSession.Header.
Session is not available from this event handler.
First of all I would create the webservice as a Xojo standalone webapp (not as a cgi).
For instance, I run several siblings of a webapp on one linux server behind a haproxy loadbalancer. This setup can handle high loads.
In your case you first must make sure that the pc which is running the webapp is powerful enough(ssd and memory) and then it most likely can handle the amount of requests you mentioned.
It also depends on the work which the webapp has to execute. If this is a time-consuming process, then you may want to hand over all incoming information to a method running in a thread and quickly return true from handleSpecialURL.
In short, whether it will work for you depends on how you design your webapp as well.