Hello,
I joined the development forum as Travis suggested. Here are some of my 
suggestions.

While
using server distributed applications (for example milky...@home and
s...@home), i haven't seen any app-info.xml in project folder location
where it enables users to control certain features over the
application; making it more specific on the demand of the user. I
believe such tweaking ability will reflect as a performance gain. The
obligation to use anonymous platform for deeper tweaking is annoying.



The second thing is the usage distribution of the CPU: It would be
great if the user is able to determine what specific project can use
how many cpu core rather than a general usage, within the preference of
BOINC client: For example i have two computers, both use server
distributed application where first uses gpu and second uses cpu
version and i don't want my first computer to use cpu applications. If
i enable cpu usage, it enables it for every computer in BOINC list and
in order to run cpu app on my second computer, i must enable the usage
preference and then my first computer will receive cpu apps also. Is
what I mean clear? The cpu usage preference shouldn't be general;
instead it must be specific to the projects.



The third thing, i did mention before: To run server distributed
app and anonymous app at the same time. It finally leads to the
existence of app.info for BOINC anyway.


So, these are my ideas. I hope it will help for the development line.


Thank you.                                        
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
_______________________________________________
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.

Reply via email to