Lists Home |
Date Index |
Rich Salz wrote:
>> Ah - now I see where you're going. Yes, a "dispatcher" service can
>> categorized in three ways:
> There is another way to look at it. The message is routed based on its
> contents; the URL is just the "main entrance," through which all
> messages have to come in. The contents of the message itself let the
> receiver determine where, internally, the message should be processed.
This is where I might be missing something (if I may jump in...).
So each message, no matter the size, should be parsed to determine
authorization, authentication and validity? As opposed to
stopping/redirecting a request based on the URL/request-credentials
before a parse happens?