Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Web Services metaphor...  RSS feed

 
Michael Dean
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is my take on the big "bang" of SOAP/XML over HTTP...am I missing the really important stuff?
From what I've seen, the Web Services model using UDDI, SOAP, WSDL provides arguable advantages in terms of network/transport:
Security/firewall: by using a text-based protocol such as SOAP over HTTP, all traffic can go over port 80 (normally, firewalls limit port access)...this infers several things:
1) Maintaining a of port numbers between producer/consumer not required
2) A single "pinch point" for control of network traffic. Running from behind a firewall becomes much less of a security issue
3) text-based traffic is easily monitored (Note: HTTP messages *can* contain binary streams coded directly into the document using Base 64 encoding)
>Complete with servlet/JSP?
Eventually, it may compete but right now it can complement. Because only one browser(to my knowledge) parses XML and it is buggy (msxml.dll), the standard approach is to use XML as a platform-neutral data format processed @ the servlet layer, which then renders HTML to the GUI layer. The Servlet/JSP model is not precluded when XML is simply the p/n data format. Thus, you still write your servlets in Java...with XML you get a neutral data format and with SOAP, you get a special type of HTTP/MIME "message type for XML-tagged data interchange.
Best Regards,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
OMNI Project
Washington State Department of Corrections
 
sridhar satuloori
Ranch Hand
Posts: 144
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most importantly SOAP is for Object Access in a platform and language independent way in a decentralised distributed environment.
With UDDI every body can expose their services like the webpages now. UDDI lists the services provided by a service provider and communication end points of the service.
WSDL is a language for communication between Service requester and Service Provider and UDDI.
Sridhar
 
Guillaume Compagnon
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WebServices/SOAP/UDDI makes me think about a way of having Corba or RMI remote Objects using IIOP or JRMP and registering in CORBA Naming or RMI Regitry but with a human-readable (or at least firewall-filterable) XML protocol.
IMHO, it is the best metaphore to define this bundle of technologies.
 
ersin eser
Ranch Hand
Posts: 1072
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
STANDARTIZATION for the Internet use for public services: it is a sci-fi
Yeah there are going to be some of them providing some services but this is not a silver bullet, there is no way this is going to be the de facto.
Security LoL
Performance LoL
I see a place for it in the intranet use & this makes it powerful since application integration is the one of the biggest market.
 
Guillaume Compagnon
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with U.
People that believe that U can make an application using WS with a good performance (response of 3s maximum) "put their finger in their eye".
For security, that should be possible (XML Signature) but for the performance it is worst.
WS is for sure not a kind toy ... it is sharp, it could make hurt!
IMHO, asynchronous messaging is the best way to use WS...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!