It was? Can you give me more detail on what you mean?
On the last point...that may be :-)
Well, it was *sort of* a workaround. I was referring to the issue described in this thread.
It required using WebServiceHostFactory3 and JsonValue as an argument type in your resource, so it probably wasn't much of a workaround for most people. I simply turned off binding to https in my local IIS as my workaround. :)