I am confused about what we want to accomplish.
A template installation, such as this one, or Saratoga or Leuven, is different from a "Standard Network" such as Awekas or WU.
Jachyms MeteoTemplate also functions as a weather-program, as it only accepts the realtime data and calculate all other values (min/max a.s.o.) on the webserver.
Upload and processing
=> For a "Standard Network" and for Jachym MeteoTemplate uploads are processed immediately on arrival at the server, stored in a database a.s.o.
=> For the other 3 templates mentioned above, the data is stored in a text file and only processed when there is a visitor to the user-website
Upload location:
=> For a "Standard Network" the upload location is one "big server" uand is the same for all members. Script name and variables are the same, different userid / passwords are used to recognize different users
=> For all templates the upload-location is different for every member => it is the private website of the template user and the name of the accepting http upload script can be different and the folder is also different in most cases.
Lets assume that a new release of the templates needs a new "template file".
If it is implemented as a "Standard Network", how would it be possible to support multiple versions?
Boris has to adept the "Standard Network"-template.
After a user restarts its MB, a new "Standard Network"-template would be used even if the target website is running the previous release.
The only problem I have found with the more then 70 Meteobridge users of the Leuven-Template is the length of the string after the ? in the URL for the HTTP upload. And therefor I totally agree with @stormchaser88 post
Hi thanks what I was asking if this could be added into meteobridge instead of having to paste all that code into .
Compare the two methods of uploading with MB:
FTP uploads with MB are as
simple and straight forward as possible.
1. Set frequency => using the dropdown.
2. Template url => type the location of the file:
http://www.mywebsite.com/myfile_to_proc ... upload.txt and hit the button if it is changed
3. Path: => type the location to store the file
httpsddocs/myfolder/myfilename.txt
One specifies the location on its server and the "template file" to process.
The "template file" can be stored in any location/folder/server.
Changing the "template file" is easy and with one press of a button, the new, customized "template file" is operational.
HTTP uploads are far more difficult for first-time users as the
location and the "
template file" are
combined into one string.
That very long string needs two extra steps which are difficult / cumbersome
1. The first part must be changed with the website / script-name to process the data
2. and then the
complete string must be copied
as one long string into a "short" field in the Meteobridge setup screen.
Solution I propose:
If Boris could split the
HTTP push services URL in
two parts, about the same as for FTP, every http upload would be as simple as
1. Set frequency => using the dropdown
2. Template url => type the
location of the file:
http://www.mywebsite.com/myfile_to_proc ... upload.txt and hit the button if it is changed
3. Process => type the script-name to accept the http request:
http://www.mywebsite.com/myscript.php?
4. Success: type whatever string needed.
Also including password processing would be far easier, only change
3. Process (or whatever name) =>
http://www.mywebsite.com/myscript.php?mypass=12345&
Implementing this in a next release of MB would also NOT affect current users as after the upgrade
=> the "Template url" field would be empty
=> and the original long combined string with location and "template file" would be in the "Process' field.
Wim
