There's a chicken and egg problem here. By definition, object storage has taken advantage of local file-systems on X86 hosts to store chunks across naive disk drives. This provides the advantage of portability and the economies of "off-the-shelf" hardware. So capacity balancing, healing, namespace management, tiering, etc are all handled at the solution/cluster level. Are designs like Isilon, Cleversafe, Caringo, etc really going to deprecate any of this to the drive component? The only real advantage I see at the system level is that the "host" mostly goes away as a fault-domain. But the huge disadvantage is the economy of scale penalty for these low-volume drives. Naturally Seagate wants margin dollars to shift from hosts to drives, but is it enough to be compelling at the system level when the system still needs to support host-style nodes??
Oh and no freaking way would this HTTP-based solution support "any application". Talk about throwing credibility out the window.