I suppose that it would be possible to derive settings from a web server, but I was imagining that if your customer was using this tool, they would be experiencing a connectivity issue. If they can't connect to the internet, there is a fairly good chance that they can't reach your web server either. Thus, the need to keep at least the default settings in a local file of some sort.
It sounds like at least some of you would like to see this tool be more versatile and be more of a general monitoring tool that can run in background all of the time. If it runs in background and constantly tests the network, I am concerned with the impact that such testing would have on wireless network performance. For instance, in a Waverider network the dynamic polling determines the percentage of time to allocate to each radio based on the frequency with which that client "talks" to the network. If every radio on the network is sending ping requests every so many minutes, the AP cannot ignore ANY of the radios and thus the dynamic polling mechanism fails to work properly. Is there any sort of workaround to this? Are radios able to ignore small packets when formulating dynamic polling allocation? - Larry _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Sent: Monday, June 09, 2008 1:51 PM To: WISPA General List Subject: Re: [WISPA] User check program Could the settings be stored in a file on a web server, and an ini file (or compiled in file) just point to the file on the web server? That way, if your network changes and you want to "re-point" everyone to different ip's, you just change the one file on your web server, not hundreds of ini files across your service area. The logo on the program could just be a pic on the web server too. So, even your company logo could be changed en mass. ~Feature Idea~ Also, something I wanted to work on some day was an icon for the notification bar (in vb.net this is easy). The icon could use different colors and the tool tip (or ~GASP~ a pop up!) to let people know of any service announcements or outages, etc. This notification could be another file on a web server that it checks every 10 minutes or so. That way, if something goes down, you don't get 2000 phone calls in a row telling you so (as long as the customer can still reach the web server...) Jason David E. Smith wrote: David, there are too many variables, I think, to have a compiled program with the settings buried into it. We will want a way to modular-ize it. Or it could be done both ways, with the option to set it to "compiled" or "INI". The compiled version WOULD make for an easier download and use, yes. Either all the variables go into an .ini file, or they all go into one file in the source code. You could even split the difference, and have default settings compiled in, that are overridden by the presence of a valid .ini. David Smith MVN.net ---------------------------------------------------------------------------- ---- WISPA Wants You! Join today! http://signup.wispa.org/ ---------------------------------------------------------------------------- ---- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ --- AV & Spam Filtering by M+Guardian - Risk Free Email (TM) --- -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
