Guidelines for new vlcs

[Damien Lucas]

A short summary of the decisions we took yesterday about the architecture of the new vlcs:

 
NETWORK:
--------
NET_init()
NET_destroy()

NET_addto_channel()
NET_removefrom_channel()
NET_user_info()
NET_machine_realinfo()
NET_update()





INTF:
-----
provides:                                     calls:

IF_init()
IF_destroy()

IF_reload_module()                           CS_reload_module()

IF_reload_submodule()                        IF_SM_start(), IF_SM_stop()

IF_addto_channel()                           CS_addto_channel()
IF_removefrom_channel()                      CS_removefrom_channel()
IF_get_user_info()                           CS_get_user_info()
IF_get_machine_realinfo()                    CS_get_machine_realinfo()

IF_update_db()                               CS_update_db()

IF_authentificate()                          CS_authentificate()




CONFIG:
-------

CFG_init()
CFG_start()
CFG_stop()
CFG_destroy()
CFG_dump()


DATABASE: Here is more a list of features than a list of functions
---------
Creation/Destruction of a table
Add/delete/search an entry
Look up of the whole database
Transactions
not multi-keys
locks with priorities (by time)
save / load table
Internal representation of data is hidden (only the size is known by DB)





Here are some more problems we found out:
- How to identify a computer ?
- How to identify a user ?
- Database update ?
- How to give config parameters to submodules
- Should we have a submodules' list written somewhere ?
- Which method to use for reload of sub-modules ?
- init/destroy/start/stop
- user_info: db/net ? 
- sub-modules "interface" ?
- Where and who we decide the user's rigth's for programs ?
- How to manage channels' methods (vls)?


OK. Just say if I wasn't clear enough !

Next time is Thursday 10th May 21h


-- 
'trox