Here's the scenario:
- Web app running on a LAN pc with (hopefully) fixed ip.
- Desktop apps ( vb or c#) apps installed on multiple pc's connected to same LAN as web app.
- Desktop apps collect data from locally connected sensors (e.g. humidity, temperature, pressure etc)
- Desktop app sensor data needs to be acquired by & displayed by web app.
- Multiple users can view web app from any pc - also on same LAN.
Each user will have the choice of which sensor(s) to view - i.e. their web page will be personalised to them, so they will need to log in as themselves & web app will remember their settings (which sensors to view).
If the web app was a desktop app i could whip this up in no time, but not having any web experience, the prospect is confusing.
I go around in circles trying to decide the best method of desktop app <> web app communications method should be in this case & I'm hoping somebody here has already done similar & is kind enough to share - at least the method if not actual code.
Some say UDP, some TCP... others say HTTP.
Being a hardened VS desktop developer, my preference for comms would be a polling method, where web app polls each desktop app in turn. This is a very familar method (with having years of modbus experience), but it may not be suitable in the web arena?
Another aspect I'm at a loss with is the user log in.
Are there any xojo examples of implementing a user log in / username, password storage, etc.?