http://bugzilla.wpkg.org/show_bug.cgi?id=230 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.meier at wpkg.org Component|wpkg.js |WPKG Client Version|other |unspecified Product|WPKG |WPKG Client --- Comment #1 from Rainer Meier <r.meier at wpkg.org> --- There is no "settings.xml" related to wpkg.js. I guess you're referring to the configuration of WPKG-client as it uses a <file /> node in the settings. Although <file2 /> is quite meaningless. To do it the proper way I would rather propose to extend the <file /> node: <file priority="10" /> Where priority is optional (defaults to a value like 10). It would allow to specify multiple WPKG locations where WPKG-client could chose from paths with same priority randomly which would allow some load-balancing too. However this might require quite some implementation effort. To achieve a simple failover maybe just adding. <file-fallback /> Might solve provide a fallback solution. Although I am sure this also requires some detection whether the primary node is available and whether it should switch to the failover instance (offline mode?). -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |