Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / May 2006

Tip: Looking for answers? Try searching our database.

ws-addressing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Viv - 19 May 2006 15:08 GMT
Hi All,
I have gone through some of the articles on ws-addressing, but couldn't
actually figure out why ws-addressing is required ?

what I understand from ws-addressing is that using ws-addressing a
response can be addressed to some other destination. For e.g. client-A
invokes a service at Server1 and requires the response to be sent to
Client-B. ws-addressing provides the standarized <wsa:ReplyTo> MI
header to achieve this. The client client-A will send a SOAP message
with <wsa:ReplyTo> element containing the url of destination endpoint
where response is to be made, in SOAP header. The server when find
<wsa:ReplyTo> element in SOAP header, will send the response to the
specified url.

Similarly From header is to send the acknowledgement back to the sender
& FaultTo to send the fault to sender/other fault handler.

Utility of EPR's (End Point Reference) is also vague.

Is this the only scenario where ws-addressing should be implemented ?

Comments/Suggestions are welcome.

Viv
Pablo Cibraro - 22 May 2006 15:24 GMT
Hi Viv,

There are three ways to route messages to a web service,

1. SOAPAction http header: This is the most common option for web services,
but it has two main problems. The http header is not secure, so anyone can
change it and route the message to a different service. It depends on http
as transport, which is bad if you are planning to host the services on
different transports.
2. Body element in the Soap Envelope. This option uses the body element name
to route the message to the right service. You can not use this option if
the body element is encrypted with message security.
3. Addressing headers. In my opinion, it is best option. The headers can be
signed so nobody can change them and they do not have dependencies with an
specific transport.

Does it make sense ?.

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

> Hi All,
> I have gone through some of the articles on ws-addressing, but couldn't
[quoted text clipped - 20 lines]
>
> Viv

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.