Multiple usage of scripts/notifications and solving of related problems

[Efried]

Running out of 8 URIs for notification, I noticed that is a possibility using the same server sided script and also WEBSET URI for sending five variables 0-999. Depending on the lenght of the GET string (compiled variables), the script could process difefrently. The only problem could be sequencing probems caused by upload time differences, if the second string arrives earlier than the first at the server.  So starting with the last sequence could make sense, otherwise some measurements could be attributed to the wrong timestamp if using the same file for server side storing. Two files using timestamps each could solve the problem.
 
 

 

[rossw]

Running out of 8 URIs for notification, I noticed that is a possibility using the same server sided script and also WEBSET URI for sending five variables 0-999. Depending on the lenght of the GET string (compiled variables), the script could process difefrently. The only problem could be sequencing probems caused by upload time differences, if the second string arrives earlier than the first at the server.  So starting with the last sequence could make sense, otherwise some measurements could be attributed to the wrong timestamp if using the same file for server side storing. Two files using timestamps each could solve the problem.

 
 
You are attempting to solve a problem that doesn't exist. I've already published sample code that does pretty much exactly what I think you're asking.
With a little forethought, the WC can operate interactively with the server and exchange an almost unlimited number of of different "things", using a single URI.
 
An example would be my weatherstation code, which "checks in" with the server periodically. When it does, the server sends a response code indicating what the WC should do next: which could be to send one of a number of environmental variables, or to instruct the WC when it should call back next, etc.
 
I have boards out there that "check in" and deliver the wind information every 5 or 10 seconds, deliver multiple temperature, humidity, barometric pressure, rainfall, NIR, PAR, UV and visible light levels, station ID, location and other data on demand... all using a SINGLE URI.