This is interesting, I recently setup a pulse-audio "network" in my house for streaming audio between rooms/backyard/etc and have thought about options for other hardware instead of full blown Linux PCs. The tablet I can see making sense as a server for the simple fact that it's easy to carry around and control/pick audio/etc, though I don't know how well it will work in that sense, especially when using combine to stream to multiple outputs, as the CPU power required to do sound synchronization (sync between local source and networked outputs) can be fairly intensive (sure you could disable local playback by not loading the sink for it, but I think the server is still the one responsible for co-ordinating/calculating sync signals between the clients). Running as a client would probably have a similiar sort of problem since the client needs to actually perform the sync adjustments/etc which take CPU power. The other big problem I can see is the wireless equation; I haven't tested the newer (0.9.10 I think is the one I'm running now) version, but on the old version I had (0.9.7 I believe) trying to do streaming over a wireless network to another PC resulted in horrible choppy sound/broken playback because of the latency the wireless network incurred.

Anyways, still very interested to see. I know the OpenWRT guys have been working on porting this to their ARM platforms for a while and have had numerous dependency problems on ARM, so if anyone who's attempting this runs into compiling issues it might be worth taking a look at the OpenWRT stuff to see if any of the problems (and answers) are similiar.