No subject

> Disallowing post responses limits the use of the more verbose
> extensions (e.g. attribute exchange).  While this might be acceptable
> for Luke's particular use case, it might leave it unsolved for others.

The POST response is a good point and clearly a valid use case, and I think=
 it's supported no matter what we decide to do. It's possible to build a re=
ceiver that handles POST params if they are present, but otherwise serves u=
p the correct cache headers and Javascript to handle the GET. That would pr=
ovide a performance boost in the common case, while still being fully compa=
tible with the spec.