El Martes 09 Jun 2009 18:28:52 Jeremy Cowles escribió: > On Tue, Jun 9, 2009 at 2:07 PM, David Anderson <[email protected]>wrote: > > Should we add that capability to the client? > > I suspect that it will open a DOS window each time it runs a batch file, > > which would rule it out for general use. > > You can use the STARTUPINFO struct to hide it (I assume this is already in > place, since we dont see other apps launch), but the security problems > combined with the extra overhead of modifying the client makes me wonder if > it's worth while. > > PyMW could do away with the script by using a compiled executable as the > main-app. All it really needs to do is find the Python interpreter and then > launch it with a couple parameters.
I wrote a BOINC science app that *embeds* the Python interpreter, avoiding any kind of process-level wrapper (like the official WrapperApp) or launch script (like your .bat), and it even provides the Python code with functions like boinc.resolve_filename(). Release pending cleanup. >From what I have seen, using a process-level wrapper (launching a real "worker" app as a separate process and keeping track of it) causes enough problems to be annoying. My opinion is that it should be used if and only if the computation code cannot be modified to use the BOINC API, be it for legal or practical reasons (like it being closed source). _______________________________________________ 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.
