Re: [boinc_dev] Work Scheduling (pt 2, Cooperative Scheduling?)

client to server transaction with a new client request. - Rom -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Wednesday, May 06, 2009 6:32 PM To: Rom Walton Cc: boinc_dev@ssl.berkeley.edu Subject: Re: [boinc_dev] Work Scheduling (pt 2, Cooperative

Re: [boinc_dev] Build documentation

Paul, it sounds like your project files are mixed up... The 6.6 branch still expects the openssl, curl, and zlib directories to be included in the BOINC directory, where as trunk expects things to be in the boinc_depends_win_vs2005 directory. First try renaming your 'boinc_depends_vs2005' to '

Re: [boinc_dev] Work Scheduling (pt 2, Cooperative Scheduling?)

?) El Jue 30 Abr 2009 21:39:27 Rom Walton escribió: The problem with persistent connections is the overall memory consumed in just maintaining the connection. Even if you striped down the scheduler to a self contained daemon you still will have to deal with the basics of maintaining connection

Re: [boinc_dev] Work Scheduling (pt 2, Cooperative Scheduling?)

The problem with persistent connections is the overall memory consumed in just maintaining the connection. Even if you striped down the scheduler to a self contained daemon you still will have to deal with the basics of maintaining connection state for which ever clients are connected and

<    1   2   3   4   5