Mark Baker wrote:
> On 1/18/06, jeffrschneider <[EMAIL PROTECTED]> wrote:
>  > Mark - you should have fun with this one... :-)
>  >
>  > 'Coarse Grain' = the level of granularity necessary to reduce the
>  > chatty-ness of an interaction. (Fatty over chatty). Typically, a
>  > coarse grain call is one that identifies a Verb + a Noun and in one
>  > call passes the adjectives and the predicates that are need to fulfill
>  > an 'action'.
> 
> A man after my own heart. 8-)  How very RESTful of you.
> 
> Actually, the way you put that reminds me of a complaint I have with
> SMTP; why the heck does it use so many round trips just to send a
> single email?  There's the welcome (HELO), setting of the sender (MAIL
> FROM), setting of the recipients (RCPT TO), then finally the sending
> of the message (DATA), each step a separate network round trip.  Why
> not use a single message with all that info in it?!  I'm sure there's
> reasons, but I suspect they're historical and no longer relevant.

SMTP works find though doesn't it?  It has more warts than just the round trips 
though.  One of the primary issues with email is the ease of anonymity.  The 
textual part of the email stays intact as it passes through multiple hops.  The 
Received-From: headers piling up.  Along the way, each hop, takes not chance at 
actually has no knowledge of if it is the first hop or the last.  Thus, the 
"from" is never validated.  Some more robust MTAs of the past, such as MMDF, 
had 
authorization mechanisms that were put in place to keep people from using paid 
for bandwidth in the UK (Steve Kille's work).  So, you couldn't gateway mail 
through his machine unless he had agreed that you were performing a useful 
service for him.

Imagine that, application level authorization and authentication!

Unfortunately, the absolutely worst MTA from a software architecture was the 
most widely distributed, and today, we still suffer from the effects of 
sendmail.  It was never intended to be a production system, and it certainly 
was 
not designed with security as a preface to its capabilities.

Gregg Wonderly





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to