about it. Transfer, transport, queueing, messaging, communication
process... Are any of you old enough to rememeber that huge extinct
construct in comms. which was referred to tersely as "OSI"? It died
out gradually in the early to mid-90s due to a combination of
American boycott (not a standard controlled there) and apathy and
inaction on the part of Europe and Japan. However there still
remains one useful relic: the OSI Reference Model!
This is still useful in terms of layering a protocol stack and
defining (hopefully) clean boundaries of demarcation of
functionality, each layer intercommunicating in what is essentially a
client/server process with the layer immediately above and below it.
Each layer is oblivious of the internal workings of its contiguously
neighbouring layers, and only needs to know and conform to their
functional interface protocols. Actual interaction is via "service
primitives". Two entities at the same stack level intercommunicate
by going up and down their respective stacks. Nothing original here
- TCP/IP works in exactly the same way.
Could this concept be usefully applied to this new thread topic?
Gervas
--- In [email protected], Sanjiva
Weerawarana <[EMAIL PROTECTED]> wrote:
>
> I'll admit, I'm one of those who cannot explain the diff if my 10
year
> son were to ask me :).
>
> Can one of the more enlightened please give concise definitions and
> explain the difference please? Please do not point me to the HTTP
spec;
> that does not help. Nor to Roy's thesis ;-).
>
> Sanjiva.
>
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
