http://bugzilla.wpkg.org/show_bug.cgi?id=91 Falko Trojahn <ftrojahn at smi-softmark.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ftrojahn at smi-softmark.de --- Comment #8 from Falko Trojahn <ftrojahn at smi-softmark.de> 2007-12-08 18:45:35 --- I think there could be an easier solution. In wpkg there is a possibility for IP based host matching. So Wpkg client, too, could check if the notebook or pc has an (DHCP) ip address within the range of the local network(s) of our company. And only in this case the installation from server will be started. Or, we do not start if the ip address is within the range of ip addresses which the vpn clients get when logging in from outer world. An extra dhcp option entry could be used, too, which isn't distributed via vpn. There are other cases where Wpkg client shouldn't start, e.g. if the size on the system drive is smaller then xx MB. Or, we could define a timeout for getting the installation file from the server. So, if after 1 minute the office file isn't there, we abort the session. But perhaps this could be an "emergency" rule only. Could be useful in situations of heavy loaded servers, too. Just my 2¢. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. -------------- next part -------------- ------------------------------------------------------------------------- just about anything Open Source. http://sourceforge.net/services/buy/index.php -------------- next part -------------- ------------------------------------------------------- Easy Software Deployment >> http://wpkg.org _______________________________________________ wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |