I hope you mean that the "sandbox" is only active when there shouldn't be network access (according to the manager/user prefs). Otherwise we can stop with our project right now.
In any case I will change our app to follow user network prefs as they are in init_data.xml. On Mon, Sep 14, 2009 at 3:13 PM, Martin <[email protected]> wrote: > Rytis Slatkevičius wrote: > > The whole nature of the project is network based and non-cpu-intensive. > > BOINC can't and won't do what we need on it's own. > > > > 2009/9/14 <[email protected]> > > > >> Please, Please, Please, let BOINC do the network communication. BOINC > may > >> have been told not to allow network communication, and you should > respect > >> that. The modem may be off, or the rates may be much higher during the > >> early evening, or ... > > Very good issue there! > > > Rytis, > > Can your application pick up and monitor the Boinc network settings and > follow them so as not to cause any user grief? > > > Should this be something that Boinc itself should control by creating a > "sandbox" to catch errant applications? > > Regards, > Martin > > -- > -------------------- > Martin Lomas > m_boincdev ml1 co uk.ddSPAM.dd > -------------------- > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
