• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Webserice fundamentals: Endpoints.

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have developed few Webservices and also worked on the client side. But there are few things which I am not sure of :

We often say that "Messages goes through many endpoints on the way to their destinations..". What does this mean exactly?

Let us say my endpoint is :

http://dev.milan.com:9080/something/services/

When and how will the message go to ANOTHER endpoint?

when does the mustUnderstand attribute in the header come into play?

I have only read it theoritically but I do not understand its actual meaning. Can it be ellaborated.

Thanks in advance,
Milan Doshi
 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think "endpoints" is not a proper term. It should use intermediates instead. These intermediates act just like network routers, forwarding the message till its final destnation.

The mustUnderstand attribute demands the message receiver have to know the meaning of the element and how to respond. Otherwise, stop processing the message further, thow an exception back to the originator.
 
reply
    Bookmark Topic Watch Topic
  • New Topic