Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We were having a discussion internally here at work about jQuery having built-in support for $.get() and $.post(), but not for $.put() and $.delete().
Some think that its to keep the js library size smaller. Others think that its not a feature that is often asked for, so is left to plugin developers to make.
What are some thoughts from the SO community?
Where do you stop?
$.options()?$.copy()?$.mkactivity()?There are too many potential HTTP verbs to bother to create a convenience method for each. Webapps haven’t bothered too much with
PUTandDELETEin the past, so they’re not used that often. The gain from a convenience method is pretty small; there’s not really any problem with just using$.ajax().