- why should boinc use grids

	- resources in general more secure and owners trusted
		- can be used for result verification 

	- resources are more stable, available, and often underutilized
		- easier to support low-latency jobs for
		example

	- resources often connected by high bandwidth links
		- could support data-intensive or data-parallel jobs

	- environment (in terms of software/libraries)
	  tends to be more homogeneous and configurable

	- easy to run the boinc client on a cluster and
		supercomputers by statically compiling a
		stand-alone client

		- examples: condor pools that run boinc jobs when
		their machines are not in use

	- leverage existing grid software
		job submission often simpler with web portals

- why should grids use boinc

	- order of magnitude more computing power and storage
	at fraction of the cost

	- many grid jobs are already task parallel,

	- challenge
		- lack of mechanisms and standards to allow
		a job submitted on a grid to run easly in
		boinc
			- cannot rely on the existance of a software stack
			- concept of an individual user or
			  job (and access rights) in BOINC
			- credit accounting for these jobs