On 01:01 19/02/03, Abbie Barbir said:
I would like to make a summary of yes and no and maybe's for the protocol
that could be (after further enhancements) presented in SFO.
Here is a quick dispatcher side list of questions I try to address right
now with "C" functions and real machines in mind. I read this list to try
to get ideas/responses, so I have not yet formalized a list of questions to
address, so it is only a few and in disorder. Different thninking it seems.
If it may help?
- is it (dispatcher) meant to be single? or to work in:
- coordination (one is master)
- cooperation (related egal)
- distribution (lose equal / specialized )
etc.
- can it delegate the dispatching role?
- on load
- by default (failure)
- on rules
- how
- what is the inter-dispatcher protocol
- does it include axfr or each dispatcher is by its own?
etc.
- which servers does it relate with?
- how the servers letit know they are there
- how does it négotiate cooperation
- how is that information memorized?
- how is it maintained (refreshed)?
- what are the recovery procedures
- are there connection/task priorities supported?
- is competing support supported?
- are there some task recovery support?
- type of channel/security support
- how is the user to remotely contol the ONES server
- information it is to pass?
- when?
- TTL?
- dissemination? When?
- reporting to the user?
- cancellation/zapping ability
- negociations
etc.
- how do we want to write the specifications of the protocol?
- plain language
- specialiized language
- specific high level language adapted to the architecture
- or work on the definitions as we progress
- "C" examples as function or a reference default
OPES dispatcher and servers.
jfc
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.454 / Virus Database: 253 - Release Date: 10/02/03