Re: OPES protocol, pre-draft
2003-03-18 11:25:14
jfcm wrote:
Notwidthstanding the document I do not understand yet what is an OPES
and what is an OPES processor - and it seems that I am not alone. But I
fully understand what is a dispatcher and what is a server.
The "data dispatcher" is part of the OPES processor (see Figure 1 and
corresponding text in the architecture draft). You might think of the
OPES processor as a physical box/network element, and about the data
dispatcher being a specific software component on this box. Note that
"OPES processor" does not refer to a "processor" in the sense of a
processor chip, but rather to the entire "box".
A little bit simplified, you might think of having two different types
of boxes in the OPES architecture - the "OPES processor" and the
"callout server". The OPES processor includes a data dispatcher
(that's simply a functional component), which decides what services
have to be executed on what messages.
Hope that helps.
-Markus
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: OPES protocol, pre-draft, Markus Hofmann
- Re: OPES protocol, pre-draft, Alex Rousskov
- RE: OPES protocol, pre-draft, Oskar Batuner
- Re: OPES protocol, pre-draft, Markus Hofmann
- Re: OPES protocol, pre-draft, jfcm
- Re: OPES protocol, pre-draft,
Markus Hofmann <=
- Re: OPES protocol, pre-draft, jfcm
- Re: OPES protocol, pre-draft, Markus Hofmann
- Re: OPES protocol, pre-draft, jfcm
- RE: OPES protocol, pre-draft, Oskar Batuner
- Re: OPES protocol, pre-draft, Markus Hofmann
- RE: OPES protocol, pre-draft, Oskar Batuner
- RE: OPES protocol, pre-draft, Alex Rousskov
- RE: OPES protocol, pre-draft, Alex Rousskov
- Re: OPES protocol, pre-draft, Markus Hofmann
Re: OPES protocol, pre-draft, Markus Hofmann
|
|
|