Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The Java Servlet API refers to a set of classes used to implement server side programs. The main player is <a href="http://docs.oracle.com/javaee/5/api/javax/servlet/Servlet.html" rel="nofollow">the Servlet</a>:</p> <blockquote> <p>A servlet is a small Java program that runs within a Web server. Servlets receive and respond to requests from Web clients, usually across HTTP, the HyperText Transfer Protocol.</p> </blockquote> <p>If you want a very simplistic analogy, the Servlet is Java's version of <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" rel="nofollow">CGI</a> (Common Gateway Interface).</p> <p>A REST API is a way to build applications by fully using the architecture of the web. Leaving all details of REST aside and grossly simplifying, it's basically a HTTP API.</p> <p>If you want to build a HTTP API, you can use Servlets. So you can also use servlets to build a REST API although there are better alternatives to that (e.g. <a href="http://en.wikipedia.org/wiki/Java_API_for_RESTful_Web_Services" rel="nofollow">JAX-RS</a>) because servlets are a "low level" component and nothing shields you from all the boiler plate code you need to write.</p> <p>You can of course call a Java application build on top of the Servlet API from other clients (e.g. from ASP.NET MVC). That's what it was built for. For this reason I don't really understand what exactly your CRM system means by a Servlet API and (a separate!?) REST API... so maybe ask the CRM provider?</p> <p><strong>EDIT :</strong> Based on what I've read about the ManageEngine Service deskPlus APIs, I'm thinking that this is just an unfortunate name chosen by the provider. </p> <p>As I mentioned in my comments, when you say <a href="http://en.wikipedia.org/wiki/Representational_state_transfer" rel="nofollow">REST</a> API you already provide some information from the beginning. Most people, when told about REST understand that you have some abstract resources, that these resources can have multiple representations (JSON, XML, whatever), that each resource is identified by a URI, that <code>/customers</code> is referring to a list of customers resources, that <code>/customers/1</code> is a customer and that <code>/customers/2</code> is another one, that you use <code>GET /customers/1</code> to find out details about the customer and <code>DELETE /customers/1</code> to delete it etc.</p> <p>REST is one way to interact with an application, another one is to expose operations that can be called by clients, for example like what <a href="http://en.wikipedia.org/wiki/SOAP" rel="nofollow">SOAP</a> is doing. Before REST became the new kid in town people were doing stuff with SOAP. Unlike accessing resources, SOAP is focused on accessing operations. When you mention SOAP to someone she knows that it's a protocol that can use HTTP's POST to transmit messages around, that each message has an XML payload that contains the operation name to invoke and the parameters needed for the call etc.</p> <p>But even before SOAP and REST becoming widely known, people realized that they can use a form submit to sneak in <a href="http://en.wikipedia.org/wiki/Remote_procedure_call" rel="nofollow">RPC</a> calls through HTTP. The HTTP form based submission is one of the methods of the API in ManageEngine Service deskPlus. But the form based submission method (as far as I know) doesn't have a cool name like SOAP or REST... so maybe that's why it was named after the Servlet API?! (I'm once again emphasizing that this is just the server implementation which is not important in the context of the HTTP protocol).</p> <p>So to conclude: Yes, you CAN call the ManageEngine Service deskPlus Servlet API from ASP.NET, even a web browser or any kind of HTTP capable client.</p>
    singulars
    1. This table or related slice is empty.
    1. POServlet API versus REST API
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBogdan
    1. USBogdan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks for the reply, then the Servlet API is a type of REST API, and i have the same question why there are two types of API ??
      singulars
      1. PO
      1. USJohn Peter
    2. CO@John Peter: The fact that it's a Servlet API is irrelevant (that's just the implementation). The protocol is the important bit, and that's HTTP. REST is also implemented (mostly) over HTTP, so I don't understand why there are two HTTP APIs. A REST API has some rules to it: you use all the HTTP verbs (GET, POST, PUT, ...), you have identifiers for all your resources, it's stateless etc. If you say Servlet API you do not communicate anything other than it accepts requests and provides a response. What's important is what is in those requests and responses! It might be a form of RPC...
      singulars
      1. PO
      1. USBogdan
    3. CO... where you call some operations on the server using GET then change it using POST (something like a legacy form of SOAP). It could be anything! As @JB Nizet mentioned, if we knew which CRM system it is, we could read the documentation and try to understand... so which CRM is it? If it's a proprietary one then ask the provider why the two API's or maybe add some more details to your question...
      singulars
      1. PO
      1. USBogdan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload