WCF REST: case-insensitive query string parameters, proposed naming convention - use underscore or?

Question

It looks like the query string parameters that you can pass to the rest method in WCF REST are case insensitive - it actually makes sense.

What is the best naming convention for two-word options using the _ character (underscore)? I never liked it, I preferred using camelCasing, but if its insensitive to the other features that I have,

for example here is my webget method

  [WebGet(UriTemplate = "?skip={skip}&top={top}&unansweredOnly={unansweredOnly}")]

Note that I have the word unansweredOnly , so I could do it unanswered_only .... or, of course, I could leave it as unansweredOnly (camelcasing), but, of course, unansweredonly would work too ... but I could would show it as UnansweredOnly in the documentation for the service.

Now, something surprising is that on the wcf leisure service's help page, it shows it as camelcasing :-)

  (from help page)  ?skip={skip}&top={top}&unansweredOnly={unansweredOnly}

I guess I'm trying to understand what everyone is doing, as well as the recommended way to do something.

I would really appreciate some reviews.

I do not want to get into a bad habit

Thanks in advance

Answer 1

http , .

WCF , ?

- , , .