Re: Thoughts on a 2.0 API

[Harrie Hazewinkel <ha...@jrc.it>]

Hi,

Maybe this thread is long gone, but here is maybe another
possible thought for the API 2.0. In addition to the ones
earlier presented.

A child startup phase; with this phase a child can
do some runtime initialisation.

An example of use:

Now mostly the scoreboard is "sync"-ed every time
when it is used (Especially with a file based
status scoreboard expensive) and written back 
afterwards. 

This phase should only at startup read/"sync" the status
scoreboard to a child internal place (done only once). 
After changes the child only writes back the changes.

We gain here a lot of "sync"-s for the scoreboard.

HH
-- 
0- Harrie Hazewinkel --------------------------------------0
 email:harrie.hazewinkel@jrc.it        phone:+39+332+789384
 http://porto.jrc.it/~harrie/            fax:+39+332+785500
 postal: Joint Research Centre of the E.C.
         CEO Programme - TP. 950
         Ispra 21020 (VA) Italy
0----------------------------------------------------------0
   Ik ben Harrie en ben 27 jaar en doe SNMP na. MIB, MIB.