How to use path param and query param in web api.

Question

0.00/5 (No votes)

See more:

Hi,

I am developing web api's using restfull web services.
How to use path param and query parm in the web api's.
Project type is asp.net mvc 4
The task is to use single method to do multiple task.
e.g public Student(string id)
{
var student=listOfStudents.find(st=>st.Id=id);
return student;
}

Posted 14-Jan-15 18:04pm

Ajay Bhalerao1

Add a Solution

Comments

Sergey Alexandrovich Kryukov 15-Jan-15 2:17am

Which query? Database? URL parameters ("query string")? What's the problem?
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sinisa Hajnal · Answer 1 · 2015-01-14T20:10:00

You shouldn't. Use single method to do single task with meaningful names.

If you absolutely have to, add parameter that describes the action i.e. public Student(string id, ActionEnum action) { /*whatever*/} where ActionEnum will list available actions in some meaningful way i.e. ActionEnum.Insert, ActionEnum.GetStudent, ActionEnum.GetStudents etc...

However, whatever you put into that enum should actually be separate method.
Note that single method will not simplify, but complicate the service.

True, you will have only one method, but the callers will have to know which parameters have to go for action. And also the method will get large with switch statements and maybe some code duplication.

Instead have a methods
GetStudents {return listOfStudents)
GetStudent (string id) { return listOfStudents.find(st :> st.Id = id)
InsertStudent (Student s) {}
etc...