Академический Документы
Профессиональный Документы
Культура Документы
15 views
Question-1: what is webservice?
Answer:
Web Services are a general model for building applications and can be implemented for any
operation system that supports communication over the Internet. Web services take advantage of
the best of component-based development. Component-based object models like Distributed
Component Object Model (DCOM), Remote Method Invocation (RMI), and CORBAs Internet
Inter-ORB Protocol (IIOP) have been around for some time. Unfortunately, they depend on an
object modelspecific protocol. Web services extend these models by communicating with
Simple Object Access Protocol (
SOAP) and XML to eradicate the barrier posed by the object modelspecific protocol.
->How is the user (consumer) at Location A aware of the semantics of the Web service at
Location B? This question is answered by conforming to a common standard. Service
Description Language (SDL), SOAP Contract Language (SCL), and Network Accessible
Specification Language (NASSL) are some XML-like languages built for this purpose. Recently,
IBM and Microsoft came together and agreed on Web Service Description Language (
WSDL) as the Web service standard.
7.stateless intraction
2.Security issue as use http(http port open for each firewall so anything come with soap
message).
issues because of XML processing, But REST too!!! If you want efficiency and your application
is inside an intranet, then use EJB with RMI over IIOP!
Question 8: when should use RESTFUL webservice?
Answer:1.The web services are completely stateless. A good test is to consider whether the
interaction can survive a restart of the server.
2.If the data that the web service returns is not dynamically generated and can be cached
3.The service producer and service consumer have a mutual understanding of the context and
content being passed along. Because there is no formal way to describe the web services
interface, both parties must agree out of band on the schemas that describe the data being
exchanged and on ways to process it meaningfully. In the real world, most commercial
applications that expose services as RESTful implementations also distribute so-called valueadded toolkits that describe the interfaces to developers in popular programming languages.
Answer:
1.The biggest conceptual difference between SOAP and XML-RPC is that XML-RPC exchanges
a limited number of parameters of six fixed types, plus structs and arrays. However, SOAP
allows you to send the server arbitrary XML elements. This is a much more flexible approach.
2.In xml-rpc we only give parameter not name of parameter it consider only order but in soap we
give name also.
**SOAP limitations:
1.A SOAP message MUST NOT contain a Document Type Declaration
2.A SOAP message MUST NOT contain Processing Instructions.
SOAP vs REST:::
1. REST has no WSDL interface definition
2. REST is over HTTP, but SOAP can be over any transport protocols such HTTP, FTP, STMP,
JMS etc.
3. SOAP is using soap envelope, but REST is just XML.