I saved that as an all file and it worked in the browser
I'm confused already. What language are you writing in? What are you creating?
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
@figuerres: But does that fit in with REST?
It feels like I'm doing it wrong with a URL like that. /shrug
I guess I'd be doing POST calls in more of an RPC style...I know it's possible with Web API, but is it "correct"?
We're in the planning stages of a new project at work here. It will be consolidating all of the shipping calculation code into one place and then exposing it via an HTTP endpoint so that any client can pass in some parameters and get the shipping cost and method returned.
We had initially chosen Web API, but I'm having trouble seeing how our use case will fit into the standard /[resources]/[identifier] URI. We don't really have identifiers, we're just passing in some data and getting some out. Our endpoint is really just a function, not accessing any data store.
Does Web API still make sense? Should we be looking at WCF? We don't need any of the advanced features of WCF, so it seems like overkill.
@blowdart: I'm jealous. We're still on Windows 7, and our IT guys haven't even started evaluating Windows 10.