I was wondering if the amount of processing done would be dependant on the speed of the user's internet connection. Just drop me a line at hambyte@vermilionweb.com
Thanks.
-Eric L. Hamric
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Typically I would hope that the kinds of tasks created for the BiggestBlue system would be for number crunching and therefore not depend on bandwidth. What still needs to be decided is if tasks that make use of a users bandwidth are something we are interested in pursuing. There are other distributed apps out there that only accept people with a 24/7 connection and are out to index the web (or something). Thing is, bandwidth is still a rather precious commodity and CPU cycles are readily available so I'd be inclined to stay away from bandwith dependant tasks at first. Perhaps at a later stage we could alway provide the facilities and let the users choose to go with these tasks or not.
Regards,
GreG
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was wondering if the amount of processing done would be dependant on the speed of the user's internet connection. Just drop me a line at hambyte@vermilionweb.com
Thanks.
-Eric L. Hamric
Typically I would hope that the kinds of tasks created for the BiggestBlue system would be for number crunching and therefore not depend on bandwidth. What still needs to be decided is if tasks that make use of a users bandwidth are something we are interested in pursuing. There are other distributed apps out there that only accept people with a 24/7 connection and are out to index the web (or something). Thing is, bandwidth is still a rather precious commodity and CPU cycles are readily available so I'd be inclined to stay away from bandwith dependant tasks at first. Perhaps at a later stage we could alway provide the facilities and let the users choose to go with these tasks or not.
Regards,
GreG