Maybe a solution is to state the content type in the *calling* sitemap. I cannot imagine a situation where your postable source could result in different content types. You want control over that, because you probably continue processing the returned data in the calling sitemap and there you cannot select between two versions. I can only think of XML processing (aka text/xml) here anyway.
So this content type will be somehow injected into the postable source and if the real content type is a different one, an exception is thrown. WDYT? Are there any counter examples? Alex -- Alexander Klimetschek http://www.mindquarry.com
