Blog Stats
  • Posts - 62
  • Articles - 11
  • Comments - 8
  • Trackbacks - 99

 

Web Services for Dummies

If I receive a message like this, whether by SMTP, FTP, HTTP, HTTPS, TCP or NNTP, I have enough information to proceed and process it.

<envelope>
    <header>
        <from>Inventory.Orders@Dell.com</from>
        <to>Accounting.Invoices@Contoso.com</to>
        <subject>Invoice</subject>
    </header>
    <body>
        <invoice>
            <!-- invoice here -->
        </invoice>
    </body>
</envelope>

Let the protocols do their job and let's keep messaging simple.

For god's sake, stop the madness and let's start exchanging messages now!

 


Feedback

# re: Web Services for Dummies

Gravatar What I am trying to say is that all the endpoint/protocol/addressing information is irrelevant to the recipient. So, why include it as part of the envelope?

Since when the mailman has to open the envelope to know the address of the recipient?

<mailer
protocol=""
channel=""
port=""
agent=""
action=""
username=""
password=""
encoding=""
content-type=""
encryption="" />

It is time to introduce a "Mailing Label" XML instruction, outside of the message to indicate the agent in charge of the transmission how to handle the message.

7/12/2004 8:18 PM | RebelGeekz

Post a comment





 

Please add 2 and 1 and type the answer here:

 

 

Copyright © RebelGeekz